(more of a plasma task, but it relates to moving things away from kdelibs4support)
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Open | None | T12187 Meta task: KDED | ||
| Invalid | None | T12180 Review all KDED modules | ||
| Open | None | T11552 Remove kdelibs4support | ||
| Resolved | ngraham | T11567 Delete khotkeys | ||
| Resolved | graesslin | T2050 sunsetting KHotKeys | ||
| Open | None | T12063 KGlobalAccel cleanup and improvement for desktop files |
Comment Actions
There are plans in plasma to drop this module.
Kglobalaccel gained ui and code to run arbitrary actions.
There's little left.
I would advise not porting this.
Comment Actions
https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/857 adds explicit support to KGlobalAccel for running any arbitrary command - even if the specified command does not have an existing desktop file. With that, it can completely replace the "command" and "K-Menu Entry" items from KHotkeys. The "DBus Command" item can be easily replicated as well, by using "qdbus" or "dbus-send" as application and specifying the right service/object/method as arguments.
This leaves the "send keyboard input" functionality that we do not currently have a replacement for. One question is if this is functionality that belongs in KGlobalAccel in the first place, or can be more easily replicated with other features. This also goes for the triggers, there are three types in KHotkeys: Global Shortcut, Mouse Gesture or Window. "Window" triggers in my opinion should be handled either by KWin scripts or KWin Window Rules. It is fairly questionable functionality in the first place. Global Shortcut triggers are handled by KGlobalAccel. This leaves mouse gestures, which probably should be its own thing somewhere.