Created attachment 165119 [details] Example of the category SUMMARY I like to bind Yakuake to Caps lock. In order to do this, I need two things: Disable the normal caps lock behavior (why the heck isnt this default :P) and do bind it instead to a key, that can be used to create a shortcut. I add the following suggestion to the project: Please create an entry in Keyboard > Advanced > Caps lock behavior (why are there two entries of this category?) and let this entry say and do: Caps lock sends F12 F12 is used to bind any application to caps lock really, and it could also be another key. (But really, use F12, its the default and established key to launch Yakuake and generally a good generic key to bind things to. People who dont use Yakuake, have it free for other things.) It could also be a custom key, but considering there is no such example in the whole KCM yet for it, I imagine the API for it has not been implemented or written yet, or it is against a design decision. Thanks STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
The Keyboard > Advanced tab is a visualization of XKB options defined in upstream project: https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config You could define your custom XKB configuration with any options you like and use it in Plasma, but this won't be reflected in the Keyboard KCM UI currently.
So far as I understand, is this dependent on X11 and considering we phase that out, is it wise to find a solution that doesnt require a component of X11, right? I guess there will be a replacement for the whole Advanced tab. I am more looking for a solution, that can actually be accieved within Plasma and not some external component.
It's not X11 specific as XKB is used for Wayland too and has common configuration with X11. Thus, the Advanced tab won't be replaced as it's on it's own place. By design, it only reflects what options are configured on XKB level, and not a thing on it's own. New XKB options shall be introduced in your custom XKB configuration. Then they can be exposed in the Advanced tab. I hope it's more clear now. *** This bug has been marked as a duplicate of bug 432818 ***