Hi,
I agree that it's most useful on plasma.
>On systems that do not use X11 (Windows, macOS, Android) it
>is most likely not useful at all.
There exists code for mac and windows but I don't know either if it's working
or just a dummy so it compiles.
Also for everyone interested in the topic,
en apps call some API of KGlobalAccel which
> results in the kglobalaccel5 process to be DBus-activated.
>
> This brings me to the question of whether there is a use case for using
> KGlobalAccel on non-Plasma systems at all. While technically
> KGlobalAccel should work on all X11 sys
This seems to happen when apps call some API of KGlobalAccel which
results in the kglobalaccel5 process to be DBus-activated.
This brings me to the question of whether there is a use case for using
KGlobalAccel on non-Plasma systems at all. While technically
KGlobalAccel should work on all X
to be DBus-activated.
>
> This brings me to the question of whether there is a use case for using
> KGlobalAccel on non-Plasma systems at all. While technically
> KGlobalAccel should work on all X11 systems most (all?) desktop
> environments have their own way of global shortcut han
-activated.
This brings me to the question of whether there is a use case for using
KGlobalAccel on non-Plasma systems at all. While technically
KGlobalAccel should work on all X11 systems most (all?) desktop
environments have their own way of global shortcut handling that we
should not interfere with
