mirror of
https://gitlab.freedesktop.org/libinput/libei.git
synced 2025-12-30 07:10:08 +01:00
2cf2425102
The text capability allows for two types of events on that interface: - XKB keysym events, e.g. XK_ssharp (0x00df) with a press/release state - UTF8 strings Keysym events are useful for scenarious where the hardware keycode is unsuitable due to potentially different key mappings on the client and server side and/or the client just not wanting to worry about those mappings. For example a client may want to send Ctrl+C instead of what effectively is now keycodes for what may or may not be a C key. UTF8 strings take this a step further and provide a full string (with implementation-defined size limits to avoid OOM). Unlike e.g. the wayland text input protocols the assumption is here that the interaction required to generate that string has already been performed before the final string is sent over the wire. Closes #73 |
||
|---|---|---|
| .. | ||
| ei-scanner | ||
| meson.build | ||
| protocol.dtd | ||
| protocol.xml | ||