-
-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement human readable Ids instead of just Command Ids in config files #3
Comments
Yeah, the CID idea was a temporary "hack" designed to make configuration quick to implement. In the final product, logid.cfg isn't meant to be edited directly; instead, logid.cfg is supposed to be auto-generated by a program. I'm planning on writing a GUI configuration utility which has human-readable diagrams of the buttons which are mapped to CIDs. |
What I like about having this on the back-end instead of the front-end is that it keeps the information centralized and independent. In the Linux world we have Gnome, KDE, Pantheon, etc, and it would be nice for any developer wanting to build a GUI to be able to use a unified system instead of redoing the same thing again. I'll get some code going, even if it isn't used in this project it'll be useful for the GUI you plan on working on. |
Well the GUI is going to interface with logid so anyone can write a GUI implementation that interfaces with it. I could also write a map with CID nicknames and CIDs. In the meantime, I'll probably drop a table of CIDs & their functions in my wiki. |
I wrote a table of CID functions over here: https://github.com/PixlOne/logiops/wiki/CIDs |
I was thinking of adding mappings from human readable button names to their respective CIds so that configuration will be more comfortable.
My thinking on how this could be done is:
I'm glad to work on this myself, but I'd like some input first (and the CIds for the MX Master 2S, if possible).
In the meantime it's also worth adding to the documentation that CIds can be found with the command:
Where device index and device path can be found with the command:
The text was updated successfully, but these errors were encountered: