[regression] MirEvent 2.0 has no replacement for mir_motion_tool_type_eraser
Bug #1422262 reported by
Daniel van Vugt
on 2015-02-16
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Mir |
Triaged
|
Low
|
Unassigned | |
| | mir (Ubuntu) |
Low
|
Unassigned | ||
Bug Description
[enhancement] MirEvent 2.0 has no replacement for mir_motion_
| Daniel van Vugt (vanvugt) wrote : | #2 |
Incomplete. I need to check the evdev stream. If it is recognised separately to the stylus then it is indeed a new tooltype.
We don't want MirEvent 2.0 to lose features we already have in MirEvent 1.0 ...
| Changed in mir: | |
| status: | Opinion → Incomplete |
| Daniel van Vugt (vanvugt) wrote : | #3 |
Confirmed in evtest ... the eraser is reported by evdev as a different tool "BTN_TOOL_RUBBER" vs the other end which is "BTN_TOOL_PEN".
So the eraser is indeed a different tool type.
| Changed in mir: | |
| status: | Incomplete → Triaged |
Daniel van Vugt (vanvugt)
on 2016-01-28
| summary: |
- [enhancement] MirEvent 2.0 has no replacement for - mir_motion_tool_type_eraser (yet) + [regression] MirEvent 2.0 has no replacement for + mir_motion_tool_type_eraser |
| tags: | added: regression |
Daniel van Vugt (vanvugt)
on 2016-05-10
| tags: | added: input |
| Michał Sawicz (saviq) wrote : | #4 |
Syncing task from Mir.
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Low |
| status: | New → Triaged |
To post a comment you must log in.
It's unclear that mir_motion_
When writing the new input event headers I decided since Qt doesn't feature it its probably not required and perhaps better expressed as some sort of modifier state on the touch.