https://bugs.kde.org/show_bug.cgi?id=486869
zkdebu...@1zk.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|0 |1
Status|RESOLVED |REOPENED
Resolution|UPSTREAM |---
--- Comment #2 from zkdebu...@1zk.net ---
>From what I understand, KWin is the one detecting the keyboard layout switch
key combination:
https://invent.kde.org/plasma/kwin/-/blob/529c3c29d300345219f3fcc173b3022c087bf32d/src/keyboard_layout.cpp#L52
The fact that the actual key translation is eventually done by libxkbcommon,
and that libxkbcommon is involved with sending the two KEYDOWN events to KWin,
do not necessarily mean that it should be the right place to resolve the
problem.
A resolution within libxkbcommon can only be done by trying to implement a
heuristic that will prevent or delay sending the second KEYDOWN event, and
maybe wait to see what is pressed next etc..
But:
1) It is a hack
2) It does not have the context of what shortcuts are being used and what
overlap there is between them, if any
(Only KWin has this information
3) Such a hack will have to be implemented also in Wayland
4) There are bugs for it in X11 for many years (see
https://gitlab.freedesktop.org/xorg/xserver/-/issues/258) and will not be
resolved
I would really love to see KDE resolving this many years old problem,
especially when Windows has the right behavior that is easy to learn from -
responding to a modifiers-only key sequence only when any modifier key is
released.
+ I would love to help with anything except coding (as my C++ is rusty, and I
don't have the dev/debug environment)
--
You are receiving this mail because:
You are watching all bug changes.
