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

[1] https://wiki.maliit.org/Wayland_Input_Method_System_Proposal [2] https://gitorious.org/maliit/maliit-framework/source/f562ad91ee14680aaafc6401428ef259a9e61598:weston-protocols/input-method.xml -- Alejandro Piñeiro ___ wayland-devel mailing list wayland-dev

Re: [Accessibility] Need to be able to sythesize mouse events

re if that would the one to go for accessibility needs, and also if implemented as a private protocol, how at-spi2 could use it. Or in other words, how declare at-spi2 as a trusted client. > > Giulio > > 2013/12/10 Piñeiro : >> GNOME Assistive Technologies need to be able to synthe

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

hat is pressed and then the client can > reply with a request to send it to the focused client too. > > Giulio > > 2013/12/10 Piñeiro : >> GNOME Assistive Technologies need to be able to listen to key events >> globally and have the possibility of consuming them. Example us

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

quires two DBUS messages. Toolkit authors want to abolish this. That's fine, *if* we have an alternative. Do we? -- Alejandro Piñeiro Iglesias (apinhe...@igalia.com) ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.fre

[Accessibility] Need to be able to sythesize mouse events

stryd/deviceeventcontroller-x11.c#n1404 -- Alejandro Piñeiro Iglesias (apinhe...@igalia.com) ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel

Re: Making Wayland accessible

pointed to that direction. > I would appreciate feedback and discussion on this. > > Has anybody else thought about these problems already ? > > Are there better ways to do these things under Wayland ? > BR -- Alejandro Piñeiro ___ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel