Will Wayland also ship with broken keyboard layout switching?
spitzak at gmail.com
Tue Oct 2 12:34:06 PDT 2012
Having read the bug, it seems extremely specific to layout switching
with shift+ctrl. However there are a lot of other identical bugs that
prevent things that are common on Windows from working on X:
1. One post mentions that hitting the "windows" key does some action,
but that makes it impossible to do windows+X shortcuts. On Windows
itself the "windows" key action only happens if you press & release it
without hitting other keys.
2. I am also aware of a nice "compose key" prefix system for Windows
that cannot be done on X. It uses the "ctrl" keys for the compose key.
You press & release ctrl and then type the compose sequence. However you
cannot do this on X without breaking all the ctrl+letter shortcuts! This
compose key prefix is a hell of a lot better than shift+altGr or
whatever X uses, which is shameful because otherwise X is much better
than Windows at compose.
I would propose that the key->event translator knows what keys are
"shift" keys. You can bind actions to them. However the action is only
triggered if the shift key is pressed & released without pressing any
other keys in between. For all other keys the bound action is triggered
when the key is pressed.
Daniel Stone wrote:
> On 2 October 2012 17:51, Ran Benita <ran234 at gmail.com> wrote:
>> Well, speaking of XKB bugs, there's this one which is inherent to the
>> We might want to consider some way to properly fix this?
> Indeed. I still can't think of a way to do this properly as such;
> using level 0 seems the closest to expectations, I think. Needs some
> more practical testing though. The main reason I didn't pursue it is
> because I think it'd end up breaking X no matter what, but it's
> something we can look at for xkbcommon.
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
More information about the wayland-devel