Mir

touchpad produces mouse events with zeroed relative_x and relative_y axes

Bug #1496814 reported by Daniel d'Andrada on 2015-09-17
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Fix Released
Medium
Andreas Pokorny
mir (Ubuntu)
Medium
Unassigned

Bug Description

If you move the mouse pointer using a touch pad, the mouse events produced always have mir_pointer_axis_relative_x=0 and mir_pointer_axis_relative_y=0.

Using mir 0.15.1 in wily

This is probably because the InputMapper in (InputReader.cpp) for Touchpads is different from the mouse cursor event mapper. Currently relative_x and relative_y is evaluated there... it might be better to evaluate it at a higher level. Or add position tracking code to the touch pad input mapper.

Related branches

description: updated
Stephen M. Webb (bregma) on 2015-09-17
Changed in mir:
importance: Undecided → Medium
status: New → Triaged
description: updated
Changed in mir:
assignee: nobody → Andreas Pokorny (andreas-pokorny)
tags: added: input
Changed in mir:
milestone: none → 0.17.0
status: Triaged → In Progress
PS Jenkins bot (ps-jenkins) wrote :

Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.17.0

Changed in mir:
status: In Progress → Fix Committed
Changed in mir:
milestone: 0.17.0 → 0.16.0
Changed in mir:
status: Fix Committed → Fix Released
Daniel van Vugt (vanvugt) wrote :

mir (0.16.0+15.10.20150921.1-0ubuntu1) wily; urgency=medium

Changed in mir (Ubuntu):
importance: Undecided → Medium
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers