https://bugs.kde.org/show_bug.cgi?id=479647
Vlad Zahorodnii <vlad.zahorod...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
|ma/kscreen/-/commit/167770b |ma/kscreen/-/commit/0b19db4
|53920ebd3c75ed5c7328ccb651c |56ff44e759e7ce4786ff84289a8
|6b6333 |96d11e
--- Comment #3 from Vlad Zahorodnii <vlad.zahorod...@kde.org> ---
Git commit 0b19db456ff44e759e7ce4786ff84289a896d11e by Vlad Zahorodnii, on
behalf of Nicolas Fella.
Committed on 23/01/2024 at 11:40.
Pushed by vladz into branch 'Plasma/6.0'.
Define display switcher shortcut via desktop file instead of at runtime
As per https://phabricator.kde.org/T12063 we want to move more towards defining
shorcuts via desktop files instead of at runtime, which has several problems
Instead of creating a KActionCollection and QAction, assigning a global
shortcut, and connecting to the QAction being triggered define a DBus call to
be executed when triggering the shortcut
This fixes several problems:
- The current shortcut is registered under the kded5 component, which not only
looks weird in the systemsettigs UI,
it also breaks in Plasma 6 where kded6 is used
- On Wayland the kded module isn't used, so nothing handles the shortcut there
currently
Related: bug 475694
(cherry picked from commit 167770b53920ebd3c75ed5c7328ccb651c6b6333)
M +0 -1 .kde-ci.yml
M +0 -1 CMakeLists.txt
M +0 -1 kded/CMakeLists.txt
M +1 -19 kded/daemon.cpp
M +2 -0 osd/CMakeLists.txt
A +13 -0 osd/org.kde.kscreen.desktop
https://invent.kde.org/plasma/kscreen/-/commit/0b19db456ff44e759e7ce4786ff84289a896d11e
--
You are receiving this mail because:
You are watching all bug changes.
