If the tracking ID changes during SYN_DROPPED, terminate the touch first
authorPeter Hutterer <peter.hutterer@who-t.net>
Thu, 6 Mar 2014 01:54:00 +0000 (11:54 +1000)
committerPeter Hutterer <peter.hutterer@who-t.net>
Fri, 7 Mar 2014 00:16:16 +0000 (10:16 +1000)
commit41334b5b40cd5456f5f584b55d8888aaafa1f26e
tree1946d38c764bad82791f961d5432104b40e64eca
parentd3ae3da90f871320de968924ef11ef1a02abc608
If the tracking ID changes during SYN_DROPPED, terminate the touch first

Most clients can't deal with tracking ID changes unless a -1 is sent first. So
if we notice that the tracking ID has changed during the sync process, send a
set of ABS_MT_TRACKING_ID -1 events for each of those, then send the rest of
the events.

Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net>
Reviewed-by: Benjamin Tissoires <benjamin.tissoires@gmail.com>
libevdev/libevdev.c
test/test-libevdev-events.c