https://bugs.kde.org/show_bug.cgi?id=318904
Thomas Lübking <thomas.luebk...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |DUPLICATE
Summary|keystrokes break with |keystrokes break with
|standart neo layout |standard neo layout
Status|UNCONFIRMED |RESOLVED
--- Comment #32 from Thomas Lübking <thomas.luebk...@gmail.com> ---
Jein, probably not in kglobalaccel.
W/o a numlock key, we cannot determine all modifiers to grab.
We could "guess" the numlock state bit (if it cannot be queried), see
https://bugs.kde.org/show_bug.cgi?id=345816#c5
But what likely should really happen is that who-or-whatever (setxkbmap?
kkeybord?) switches to this funky layout should clear the numlock state from
the server before removing the concept of a numlock key (which usually exists
even if you've no key for it like on a notebook, the problem is that the key is
remapped)
Also this is bug #345816
*** This bug has been marked as a duplicate of bug 345816 ***
--
You are receiving this mail because:
You are watching all bug changes.
