https://bugs.kde.org/show_bug.cgi?id=366608
--- Comment #10 from Matthias Fauconneau ---
1)
Works for me with Brightness Up (F7), Volume Down (F9) and Up (F10).
But strangely Brightness Down (F6) still does not repeat.
I see no difference between the keys
https://bugs.kde.org/show_bug.cgi?id=366608
Martin Gräßlin changed:
What|Removed |Added
Status|CONFIRMED |RESOLVED
https://bugs.kde.org/show_bug.cgi?id=366608
Martin Gräßlin changed:
What|Removed |Added
Status|UNCONFIRMED |CONFIRMED
Ever
https://bugs.kde.org/show_bug.cgi?id=366608
Martin Klapetek changed:
What|Removed |Added
CC||mklape...@kde.org
---
https://bugs.kde.org/show_bug.cgi?id=366608
--- Comment #6 from Martin Gräßlin ---
> So KWin/Wayland requires non-Qt applications to link with KGlobalAccel to
> register shortcuts ?
This is getting off-topic.
--
You are receiving this mail because:
You are the assignee
https://bugs.kde.org/show_bug.cgi?id=366608
--- Comment #5 from Matthias Fauconneau ---
I think notifying release events would be a better solution since it would
allow smoother/finer brightness adjustments than the low rate of key
repeats.
So KWin/Wayland
https://bugs.kde.org/show_bug.cgi?id=366608
--- Comment #4 from Martin Gräßlin ---
KGlobalAccel actions are only triggered on press events. There is no additional
call when they are released.
I played a little bit with my system and there the brightness key sends
https://bugs.kde.org/show_bug.cgi?id=366608
--- Comment #3 from Matthias Fauconneau ---
I think not repeating global shortcuts is the correct behaviour.
Still it would make sense for PowerDevil to be notified when the shortcut
is released.
I am not clear on how
https://bugs.kde.org/show_bug.cgi?id=366608
--- Comment #2 from Martin Gräßlin ---
Just checked, kwin explicitly ignores key repeat events to trigger global
shortcuts
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.kde.org/show_bug.cgi?id=366608
Martin Gräßlin changed:
What|Removed |Added
CC||mgraess...@kde.org
---
10 matches
Mail list logo