AreaBottomEdge is not always ignored and sometimes causes other touches to be ignored
Submitted by Jeremy Huddleston Sequoia
Assigned to Peter Hutterer
I have a clickpad, and I'm trying to get synaptics to behave well with it.
I really want an "IgnoreThumb" option which would allow me to have one finger (my thumb) pressing down on the button while the other finger drags (eg an icon).
To approximate that, I decided to try defining AreaBottomEdge (to 85%). If I move my finger into that region, the mouse cursor stops moving. Great. The only problem is that if I have a finger in that region, ALL movement is ignored (not just the one within that region).
- If I am moving my finger in the region above the bottom, the cursor will move, but as soon as I touch the bottom region with another finger, the cursor will stop moving, and scroll events will be generated instead (because it sees two fingers).
- In the opposite case, if I start with one finger in the bottom region and then place another finger above it and start moving it, there is no cursor movement nor scroll events.
In both of those example cases, I would expect the touch in the AreaBottomEdge to be ignored and the movement above the edge to translate the cursor.