https://bugs.kde.org/show_bug.cgi?id=476550
Jakob Petsovits <jpe...@petsovits.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |CONFIRMED
Ever confirmed|0 |1
CC| |jpe...@petsovits.com
--- Comment #7 from Jakob Petsovits <jpe...@petsovits.com> ---
So as far as I understand, there are different parts to this issue:
1. The user changes monitor brightness via monitor OSD, also because Plasma
doesn't provide per-display controls at the moment. DDC/CI doesn't tell us that
a change was made, that's not part of the protocol. PowerDevil would have to
read each monitor's current brightness manually before initially dimming, so we
know what values to return to. This is essentially Bug 411050 comment #10, and
not straightforward to fix. Setting brightness via Plasma brightness controls,
or setting brightness before PowerDevil starts (i.e. before login), would be a
workaround to not keeping up to date on the latest brightness values.
2. The current brightness setter API only takes a single brightness value, and
that value is not adjusted for different monitors. I opened this MR to sidestep
this legacy brightness setter API and instead control dimming with a brightness
multiplier: https://invent.kde.org/plasma/powerdevil/-/merge_requests/360
3. There's also an issue in setBrightness() in that it doesn't adjust its
single value to the different possible maximum brightness values of each
monitor that's getting changed. I have a patch to fix that as well, no MR yet,
but that's less important here because we're sidestepping setBrightness()
anyway as per the previous point.
--
You are receiving this mail because:
You are watching all bug changes.
