touchpad produces mouse events with zeroed relative_x and relative_y axes
Bug #1496814 reported by
Daniel d'Andrada
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
Fix Released
|
Medium
|
Andreas Pokorny | ||
| mir (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Bug Description
If you move the mouse pointer using a touch pad, the mouse events produced always have mir_pointer_
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
lp:~andreas-pokorny/mir/fix-1496814
- Daniel van Vugt: Approve
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Alan Griffiths: Approve
-
Diff: 79 lines (+19/-4)1 file modified3rd_party/android-input/android/frameworks/base/services/input/InputReader.cpp (+19/-4)
| description: | updated |
| 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 |
Revision history for this message
| PS Jenkins bot (ps-jenkins) wrote | #1 |
| 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 |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #2 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Fix Released |
To post a comment you must log in.
Fix committed into lp:mir at revision None, scheduled for release in mir, milestone 0.17.0