Open joaocandre opened 5 months ago
daitj
commented
3 months ago Yeah this is expected, refreshing slider when you open will be slow as ddcutil itself takes some time to report these values back. Perhaps if we use ddccontrol, like mentioned in #137, there might be a way to listen for changes, don't know yet, this needs some investgation.
joaocandre
commented
3 months ago It being slow is, as you say, expected. But what I reported was that it doesn't update at all if you adjust brightness using the physical buttons on the display (or just run ddcutil separately).
I'm assuming the brightness level is only updated on each manual increment using the slider, while perhaps for it reflect the actual state of the display you'd need to be frequently polling the level on the background (or, for less overhead, just trigger an update whenever the system menu is opened).
daitj
commented
3 months ago During initial developement I tried to fetch the values when after menu was open, it introduced some lag between the slider is visible with old value and then gets updated with current value set manually.
Frequent polling is not the answer. But adding an extra fetch when menu is opened is not a big deal, if you can live with the lag.
Describe the bug The slider in Gnome menu does not update brightness level if adjustments are made without the extension.
To Reproduce Adjust display brightness through any alternative means, such as: physical controls on the display, daemons such as clight or call
ddcutildirectly (e.g.ddcutil setvcp 10 90). Regardless of how brightness is set, the level reported by the extension won't change.Delete cache file if it exists and try again No
~/.cache/ddcutil_detecton my system.Journal logs
Desktop (please complete the following information):