[enhancement] Expose mouse event information over DBus for Autopilot

[Thomi Richards]

We currently have keyboard and touch uinput drivers. We need a mouse driver as well.

[Thomi Richards (thomir-deactivatedaccount)]

This work cannot be completed until we have input bindings for mir, since mice send relative movement events, and we need to know the current mouse cursor position.

[kevin gunn (kgunn72)]

lower priority - for the moment all eyes are on phone v1, this would need to be post v1 unless we have no bugs

[Daniel d'Andrada (dandrader)]

This probably belongs to mir instead of unity8, as I believe that defining a mouse pointer is a mir affair.

I find it difficult to work on this item before we have started working on a cursor/mouse pointer in mir-unity8 in the first place (i.e. "mir-unity8 on the desktop").

[Daniel van Vugt (vanvugt)]

Can someone please clarify what's missing here? Mir has had working mouse events since the start of the year.

Should the title say "for Autopilot"?

[Thomi Richards (thomir-deactivatedaccount)]

The work item is to expose mouse event information over DBus. I've updated the bug title accordingly.

Autopilot needs a way to work out what the current mouse cursor position is. Whether that comes from unity8 and a dbus interface, or from mir and some other form of IPC doesn't really matter much.

Whatever we do, it should minimise latency in the communication between the AP test suite and the other end (mir/unity8)

[Leo Arias (elopio)]

Back to new as thomi has provided the information requested while marking it incomplete.

[Thomi Richards (thomir-deactivatedaccount)]

Why the change in priority? This is still as important as it was.

While this is less important than anything RTM-related, it's still required before we can test unity8 as a desktop shell, so is certainly more important than "wishlist".

[Daniel van Vugt (vanvugt)]

Sorry, "Wishlist" is just the official classification for any enhancement in Launchpad. I've bumped it back to Medium.