Commit cd574ed5 authored by Peter Hutterer's avatar Peter Hutterer

touchpad: add a note to the synaptics touch restore feature

We have code in place to handle the quirky transition from two to three
fingers (where one slot ends and another one starts). We do not handle the
same issue when transitioning from three to two fingers.

This is a note only because it hasn't mattered so far, at least until
eb6ef9fe from #408. And it doesn't matter anymore now either
because that code is now only called for ALPS devices.

#434 (comment 419912)Signed-off-by: Peter Hutterer's avatarPeter Hutterer <peter.hutterer@who-t.net>
parent 7b949556
......@@ -609,11 +609,14 @@ tp_restore_synaptics_touches(struct tp_dispatch *tp,
(tp->nfingers_down == tp->num_slots && nfake_touches == tp->num_slots))
return;
/* Synaptics devices may end touch 2 on BTN_TOOL_TRIPLETAP
* and start it again on the next frame with different coordinates
* (#91352). We search the touches we have, if there is one that has
* just ended despite us being on tripletap, we move it back to
* update.
/* Synaptics devices may end touch 2 on transition to/fro
* BTN_TOOL_TRIPLETAP and start it again on the next frame with
* different coordinates (bz#91352, gitlab#434). We search the
* touches we have, if there is one that has just ended despite us
* being on tripletap, we move it back to update.
*
* Note: we only handle the transition from 2 to 3 touches, not the
* other way round (see gitlab#434)
*/
for (i = 0; i < tp->num_slots; i++) {
struct tp_touch *t = tp_get_touch(tp, i);
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment