-
Notifications
You must be signed in to change notification settings - Fork 68
Problematic default key bindings #141
Comments
Yeah, finding keys never was my strong suit. Any ideas? I'd also be okay with dropping some shortcuts, at least by default, though I'm not quite sure what happens with old settings after an upgrade? |
Recently I hit this and tried looking for a KDE bug pertaining to how shortcuts are presented in the UI. It seems that former representation (involving explicit Shift key) feels more natural and should be preferred to the latter representation. |
Yeah, I'm not much of a UX expert either. I have the conflicting keys mapped on Meta + Shift + PgUp.
Yes perhaps, but which ones are those you want to cut off? :)
My bet would be that the old shortcuts will be preserved. I'll test it later today.
Agreed. But it's not the matter of preference - the problem is that the "nicer" shortcuts just do not work for me with standard US layout. |
Yeah, that should work (though I have to admit, Meta + PgUP is a horrible shortcut for maximization, and it'd surprise me if anyone actually used it).
Mostly anything that can be done via KWin's shortcuts should not be in the script, though I've removed most of those already. "Tile now" is a hack that I don't think is all that useful? Do we need both "move window up/down/left/right" and "swap tile with next/previous"? "Toggle Border For All" is basically just "do what KWin does, for all windows", and I don't think it's used often. |
:)) I do! No kidding. On my NB keyboard it even is Meta + Fn + Up and yet I still use it.
I can imagine that there are users out there who have tiling off by default an only use the script to unclutter their desktops occasionally.
I do personally only use "move window". "Swap tile" is too confusing to my aging brain.
Can not tell, since I use regular Breeze decorations without title bars. I don't feel any needs to turn them off. |
So, I've just tried to change these, and in the process I reset all shortcuts to the defaults, and it doesn't seem to be registering? I updated the script, restarted kwin, ran kbuildsycoca5 for good measure, and all the tiling shortcuts appear unset? Is this broken again? #79? This is with kwin 5.15.4. |
I just tested on KWin 5.15.3. Created a new user, logged in, installed the script, ran kbuildsycoca5 and all the shortcuts are assigned. I'll retest with KWin unstable later today. |
KWin uses that for maximize/minimize. No idea why you'd want to press that, but that's the way the cookie crumbles. Fixes #141.
Urgh... it doesn't change the defaults for "known" shortcuts. You need to remove the script, remove inactive shortcuts, then reinstall. |
Mmm, too bad. There's not much we can do about it though, except for mentioning it in the README. |
We have some conflicting default key bindings:
Next tiling layout - Meta + PgUp is used by KWin for "Maximize Window".
Previous tiling layout - Meta + PgDown is used by KWin for "Minimize Window".
Then we have some default shortcuts that do not work on standard US keyboard layout:
Swap with next tile - Meta + Shift + [ - there is no such key. It's Meta + {.
Swap with previous tile - Meta + Shift + ] - there is no such key. It's Meta + }.
The text was updated successfully, but these errors were encountered: