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
Support for new monitor overrides feature? #12
Comments
Store just calls clight dbus Store method. |
ah, that is strange.... it could be a clight issue if it doesn't work on the latest master, but I will look into adding the option in the gui in a bit |
It did not work on a build from yesterday, and unfortunately can't test again for a few days. Will update then. |
Hi, i have finally gotten around to looking into adding the feature. Unfortunately Clight does not expose these properties under the DBus interface... @FedeDP , is this something that is on the roadmap? however i would be happy to add it to the Sensor tab, perhaps under a dropdown for each monitor ID |
Hi! |
+1 |
Hi! |
looks good! ill be brainstorming a good implementation and ill get something working in a bit :) |
In my opinion, it would be best to present the user with a list of specific curves used right now by Clight (ie: calling List()), then a "+" button to add a new one (and a "-" button to remove already present ones); Note: to remove a specific curve ("-" clicking) you should just pass its serial and 2 empty arrays, eg: |
that sounds like a good idea |
Ah you are working on it. Alright :) |
i finally merged the PR, let me know if there are any issues.... |
i notice that if I add a monitor override manually to the .conf and then changes some settings in GUI and press store, the monitor override is deleted!
could this be fixed?
and of course, also, a new Tab in the GUI to insert custom monitor overrides, when you have time.
thanks
The text was updated successfully, but these errors were encountered: