On Tue, Jul 22, 2014 at 11:23 AM, Luke Yelavich
<luke.yelav...@canonical.com> wrote:
On Tue, Jul 22, 2014 at 09:42:42AM EST, Gerry Boland wrote:
Hey folks,
in working on QtCompositor, I stumbled across a problem ([1]).
Autopilot needs to know the position of items in an application
(buttons, etc) in screen coordinates - not surface. It needs that
as it
generates inputs via uevent, which are defined in screen
coordinates.
Qt's accessibility framework also needs to be able to present this
information via at-spi to accessibility tools such as Orca.(1) This
is probably something that is more to do with Qt internals working
with Mir, but even though this is primarily about autopilot, keeping
accessibility requirements in mind when thinking about this is
probably also relevant.
My memory of our discussions in Malta was that it seemed like a good
idea for Mir itself to take some part of the role of the at-spi
registry and have toolkits report the surface-relative positions of
their widgets. Then Mir can provide (appropriately permissioned)
accesibility applications the absolute positions of the various widgets.
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/mir-devel