[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD

2024-05-08 Thread Zamundaaa
https://bugs.kde.org/show_bug.cgi?id=470106

--- Comment #5 from Zamundaaa  ---
Git commit 2f7649edc535c68e1906c2dd3b14152e0ed9f0b9 by Xaver Hugl.
Committed on 08/05/2024 at 21:41.
Pushed by zamundaaa into branch 'master'.

applets/brightness: fix max brightness change notification

The wrong signal name was used, which meant the maximum brightness value of the
slider and the actual maximum powerdevil uses could get out of sync

M  +1-1applets/brightness/plugin/screenbrightnesscontrol.cpp

https://invent.kde.org/plasma/plasma-workspace/-/commit/2f7649edc535c68e1906c2dd3b14152e0ed9f0b9

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD

2024-05-08 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470106

--- Comment #4 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/4294

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD

2024-03-18 Thread Jakob Petsovits
https://bugs.kde.org/show_bug.cgi?id=470106

Jakob Petsovits  changed:

   What|Removed |Added

 CC||jpe...@petsovits.com

--- Comment #3 from Jakob Petsovits  ---
New merge request @
https://invent.kde.org/plasma/powerdevil/-/merge_requests/342.
It fixes the brightness slider lagginess and makes the slider jump way less,
still possible but negligible in practice.

I have deeply pondered what this means for the slider going out of sync with
the OSD. Quick testing now seems fine in terms of showing the right OSD values
after quickly dragging the brightness slider. It may just all be a question of
"how much time do you give powerdevil to apply the new brightness slider value
before pressing the brightness key". In which case, the answer is "it needs a
lot less time to apply the new brightness than it did before (but there is
still a little delay theoretically)".

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD

2023-08-13 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=470106

Bug Janitor Service  changed:

   What|Removed |Added

 Status|CONFIRMED   |ASSIGNED

--- Comment #2 from Bug Janitor Service  ---
A possibly relevant merge request was started @
https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3178

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD

2023-05-23 Thread ratijas
https://bugs.kde.org/show_bug.cgi?id=470106

ratijas  changed:

   What|Removed |Added

   Assignee|plasma-b...@kde.org |m...@ratijas.tk
 Status|REPORTED|CONFIRMED
 Ever confirmed|0   |1

--- Comment #1 from ratijas  ---
I also noticed that moving slider fast can get it out of sync or revert (sync)
to an intermediate state. So I trust your bug report even without screenshots
(:

Probably backend needs some job buffering and proper ordering. I've done
something like that in my personal DDC/CI brightness control app, so I should
take a look at it in Plasma powerdevil too.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Powerdevil] [Bug 470106] brightness-control slider shows different percentage than OSD

2023-05-23 Thread Nate Graham
https://bugs.kde.org/show_bug.cgi?id=470106

Nate Graham  changed:

   What|Removed |Added

  Component|general |general
   Target Milestone|1.0 |---
 CC||m...@ratijas.tk,
   ||natalie_clar...@yahoo.de,
   ||n...@kde.org
Product|plasmashell |Powerdevil

-- 
You are receiving this mail because:
You are watching all bug changes.