Hello, Digging back on this.
Peter Hutterer, le lun. 08 déc. 2014 16:05:56 +1000, a ecrit: > Some devices don't rely on keycodes + xkb layout but rather send a specific > keysym (or multiple) in response to physical button presses. This is the case > for chorded keyboards for example. > > This adds a new type of key event that provides UTF8 strings. The > press/release pair applies to this type as well, the exact behavior of when > the release event is sent is implementation dependent. > > Signed-off-by: Peter Hutterer <peter.hutte...@who-t.net> > Cc: Samuel Thibault <samuel.thiba...@ens-lyon.org> > --- > Not intending to merge this yet, this is supposed to spark some discussion. > We don't have real support for this in the kernel and I don't have access to > any device that really generates keysysms. PoC is in Patch 2, but in the > real world the device will likely be hooked up through some other means than > evdev. > > Until we have reliable testing and know what the details need to be for > device support, this remains an RFC (but now archived on the list instead of > just locally). Thanks for this! Unfortunately it remained a chicken-and-egg thing for these years. I don't know how I can plug something that would produce such events. I can easily write a brlapi module that takes input from a braille device and emits string events, I just don't know how to plug it into the libinput stack. Perhaps somebody could write (or point me to) a dumb libinput piece skeleton which I'll be able to fill? Samuel _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-devel
