From 917b79f83e4f659a669752396c76fbe6cdad3be0 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Mon, 29 Jul 2024 14:27:06 +1000 Subject: [PATCH] proto: clarify the ei_keyboard.modifier event a bit This is an event in response to "something change the modifier state" where "something" was not an ei_keyboard.key event on this interface. Examples are NumLock on after resumed, a nonzero XKB group, etc. Closes #57 --- proto/protocol.xml | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/proto/protocol.xml b/proto/protocol.xml index dbb11ff..1b8cc62 100644 --- a/proto/protocol.xml +++ b/proto/protocol.xml @@ -1355,9 +1355,14 @@ - Notification that the EIS implementation has changed modifier - states on this device. Future ei_keyboard.key requests must take the - new modifier state into account. + Notification that the EIS implementation has changed group or modifier + states on this device, but not necessarily in response to an + ei_keyboard.key event. Future ei_keyboard.key requests must take the + new group or modifier state into account. + + This event should not be sent in response to ei_keyboard.key events + that change the group or modifier state according to the keymap. The + client is expected to track such group or modifier states on its own. A client must assume that all modifiers are lifted when it receives an ei_device.paused event. The EIS implementation