(In reply to comment #88) > (In reply to comment #86) > > Already proven to break the XKB specification, yes. > > Hi Daniel. I've seen this comment about breaking the XKB specification in > several places and - I'm really not trying to be contrary - I looked at the > protocol specs here > http://www.x.org/releases/current/doc/kbproto/xkbproto.html > and I can't understand how this behavior change contradicts the spec. > > Now - I'm not a trained X11 developer, and I'm not even that good at reading > specs, so I would really appreciate it if you can point me at the section > relevant to the breakage you discuss, so I can be more informed about the > issue. > > Thanks in advance.
Hi Oded, It is not in XKBproto but in XKBlib spec. You can see the only assertion against changing layout on release in general (and the patch in particular) in ftp://ftp.x.org/pub/X11R7.0/doc/PDF/XKBlib.pdf, "Table 16.4 Group Action Types", the last item XkbSA_LockGroup, citing: " 1. If the XkbSA_GroupAbsolute is set in the flags field, key press events set the locked keyboard group to the group specified by the group_XXX field. Otherwise, key press events add the group specified by the group_XXX field to the locked keyboard group. In either case, the resulting locked and effective keyboard groups are brought back into range depending on the value of the groups_wrap field of the con-trols structure. 2. A key release has no effect. " -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/36812 Title: Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/36812/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
