[Accessibility] Need to be able to register for key events globally

Giulio Camuffo giuliocamuffo at gmail.com
Wed Dec 11 10:14:34 PST 2013

Not currently.
I'm not sure what you mean with consumed. Do you mean that a not
consumed event is still received by the client that has the focus
while a consumed one is not?
If so, i guess a protocol could be developed where the compositor
sends an event with the key that is pressed and then the client can
reply with a request to send it to the focused client too.


2013/12/10 Piñeiro <apinheiro at igalia.com>:
> GNOME Assistive Technologies need to be able to listen to key events
> globally and have the possibility of consuming them. Example use
> cases:
> * Orca's presentation of navigation (Events not consumed)
>   - Right Arrow: Speak character moved to (right of cursor)
>   - Shift Right Arrow: Speak character selected (left of cursor)
>   - Down Arrow: Speak next line
>   - Etc.
> * Orca's navigational commands (Events consumed)
>   - H/Shift + H: Move amongst headings
>   - NumPad 8: Speak the current line
>   - NumPad 5: Speak the current word
>   - NumPad 2: Speak the current character
>   - Etc.
> Current solution: The Orca screen reader calls AT-SPI2's
> atspi_register_keystroke_listener(). AT-SPI2 then notifies Orca of key
> events it receives from the toolkit implementation of ATK method
> atk_add_key_event_listener(). Applications then have to wait for Orca
> to consume the event or not. This requires two DBUS messages. Toolkit
> authors want to abolish this. That's fine, *if* we have an
> alternative. Do we?
> --
> Alejandro Piñeiro Iglesias (apinheiro at igalia.com)
> _______________________________________________
> wayland-devel mailing list
> wayland-devel at lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/wayland-devel

More information about the wayland-devel mailing list