[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdelibs-bugs
Subject:    [frameworks-kglobalaccel] [Bug 339838] Cannot use Tab for global shortcuts anymore
From:       Bernd Steinhauser <linux () bernd-steinhauser ! de>
Date:       2015-05-27 19:49:00
Message-ID: bug-339838-90985-qDR30BOIZV () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=339838

--- Comment #15 from Bernd Steinhauser <linux@bernd-steinhauser.de> ---
(In reply to Hans Meine from comment #12)
> Sounds like bug #341959 contains an explanation indeed.  However, creating a
> unit test for this requires deep X11 knowledge.
I don't think so. That bug reminds me very strongly about bug 338487, which was
caused by an upstream Qt bug. See the Qt bug Florian Jacob linked there. So in
case of bug 341959, it would be interesting, if it occurs after said patch was
applied to Qt (or when a newer Qt is used. I think >=5.4.1 should be ok).

> I do not even understand how Neo implements six layers (see
> http://www.neo-layout.org for an immediate preview of the layout) when there
> may only be up to four KeySyms associated with a KeyCode.
xkb has a concept of a level5 modifier. I think it would be possible to get up
to 9 layers.
Neo doesn't use those due to ergonomic reasons, as Shift+M3+M4+Key wouldn't
really be feasible anyway (and possibly not working on some keyboards due to
hardware restrictions).
Shift+M4 also isn't considered as a separate layer, since you might want to use
Shift in combination with the movement keys on layer 4 to select text.

It's a very clever concept if you spend the time to learn it.
I'm glad I did so approx. 7-8 years ago. ;)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
Kdelibs-bugs mailing list
Kdelibs-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdelibs-bugs

[prev in list] [next in list] [prev in thread] [next in thread]