MirMotionEvent action field not consistent
Bug #1320219 reported by
Sylvain Becker
This bug report is a duplicate of:
Bug #1311699: MirMotionEvent.action needs stronger typing (to MirMotionAction etc).
Edit
Remove
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
New
|
Undecided
|
Unassigned |
Bug Description
With a touch screen and multi-touch, sometimes MIR sends (rarely) MirMotionEvent.
It sends motion.action == 0x101
"motion.action >> 8" refers to the index in the array "pointer_
"motion.action & 0xff" refers to the "action", here mir_motion_
But pointer_count == 1 (size of the array "pointer_
So the "motion.action" refers to an unreachable element of the array.
To post a comment you must log in.
Good catch. This is a known issue and already has a bug number 1311699, so directing you there...