[enhancement] Expose mouse event information over DBus for Autopilot

Bug #1169362 reported by Thomi Richards on 2013-04-15
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Autopilot
Medium
Unassigned
Mir
Won't Fix
Medium
Unassigned

Bug Description

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

Changed in autopilot:
milestone: none → 1.3
Changed in autopilot:
status: Confirmed → In Progress
assignee: nobody → Thomi Richards (thomir)
Changed in autopilot:
milestone: 1.3 → 1.3.1

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.

Changed in autopilot:
status: In Progress → Triaged
Changed in unity8:
importance: Undecided → High
assignee: nobody → Daniel d'Andrada (dandrader)
Changed in unity8:
milestone: none → ubuntu-13.12
kevin gunn (kgunn72) wrote :

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

Changed in unity8:
status: New → Triaged
Changed in autopilot:
importance: High → Medium
Changed in unity8:
importance: High → Medium
summary: - Need a mouse backend that uses UInput
+ Support mouse event information

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").

affects: unity8 → mir
Changed in mir:
milestone: ubuntu-13.12 → none
Daniel van Vugt (vanvugt) wrote :

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"?

Changed in mir:
status: Triaged → Incomplete

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)

summary: - Support mouse event information
+ Expose mouse event information
Leo Arias (elopio) wrote :

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

Changed in mir:
status: Incomplete → New
summary: - Expose mouse event information
+ Expose mouse event information over DBus
Changed in mir:
importance: Medium → Wishlist
status: New → Triaged
summary: - Expose mouse event information over DBus
+ Expose mouse event information over DBus for Autopilot

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) wrote :

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

Changed in mir:
importance: Wishlist → Medium
tags: added: enhancement
summary: - Expose mouse event information over DBus for Autopilot
+ [enhancement] Expose mouse event information over DBus for Autopilot
Changed in mir:
assignee: Daniel d'Andrada (dandrader) → nobody
Changed in mir:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers