https://bugs.kde.org/show_bug.cgi?id=500997
Sanfod Rockowitz <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #8 from Sanfod Rockowitz <[email protected]> --- Some observation here: ddcutil does not report changes to feature values. In principle, the Monitor Command Control Set (MCCS) spec provides for this; in practice it's unreliable. For details, see my response to this recent feature request (https://github.com/rockowitz/ddcutil/issues/589). Regarding different brightness values for different modes, VCP feature xDC (Display Mode) is supposed to report the current mode. It's implemented for some monitors. PowerDevil could conceivably use that feature to maintain different brightness values (feature x20) for different modes. But then the question becomes one of detecting mode changes and changing the current UI value accordingly. Finally, some of the comments seem to assume that a slider value in the range 0..100 should be written verbatim to feature x10. This is not what happens. In addition to the current value, the response to "getvcp x10" reports a maximum value as well. That's commonly 100, less frequently 255, but can even be a 2 byte value - my NEC P241W has a maximum value of 360. The brightness value shown in the PowerDevil widget is the percentage of maximum value. -- You are receiving this mail because: You are watching all bug changes.
