mir_touch_axis_touch_major always returns 0 on laptop touchscreen
Bug #1511527 reported by
Alberto Aguirre
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
New
|
Undecided
|
Unassigned | ||
| mir (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
An Asus UX302L which has an Atmel Atmel maXTouch Digitizer,
mir_touch_
evtest does not report any ABS_MT_TOUCH_MAJOR but shouldn't the input stack default to a value of 1.0 if that's the case?
Revision history for this message
| Michał Sawicz (saviq) wrote | #2 |
To post a comment you must log in.
Hmm, maybe zero is a sane default on devices that don't know the answer. In that case we may want to push responsibility for this all the way to the app.
That might be nicer than defaulting to 1 because a value of 1 in some apps (like fingerpaint) is both valid and pointlessly small (too small to see on high res displays). So zero might actually be better, and let the app change its behaviour.