Skip to content

#680: Avoid processing the last hold and motion event twice

José Expósito requested to merge JoseExposito/libinput:issue-680 into main

During the transition from GESTURE_STATE_HOLD_AND_MOTION to GESTURE_STATE_POINTER_MOTION the last pointer motion event was processed twice.

Fix #680 (closed)

As a side note, I'm not sure if we could change tp_gesture_post_gesture to use a switch instead of a bunch of ifs.

Been able to concatenate states makes difficult to reason about the state machine. However, I'm not sure if some state transition rely on this to work/not drop an event.

Merge request reports