-
Bug
-
Resolution: Fixed
-
P5
-
8u20
The first line of a log of raw native input events is shown twice. For example, when running MultiTouch2Test.twoFingerDrag with device EGalaxMultiTouchDevice1 and -D-Dmonocle.input.traceEvents=true -Dmonocle.input.traceEvents.verbose=true we see:
traceEvent: Read EV_ABS ABS_MT_TRACKING_ID 1
traceEvent: Read EV_ABS ABS_MT_TOUCH_MAJOR 0
EV_SYN SYN_MT_REPORT 0
traceEvent: Read EV_SYN SYN_MT_REPORT 0
0.002 TestLog: TestTouchDevice: sync
EV_SYN SYN_REPORT 0
traceEvent: Read EV_SYN SYN_REPORT 0
traceEvent: Processing EV_ABS ABS_MT_TRACKING_ID 1
traceEvent: Processing EV_ABS ABS_MT_TRACKING_ID 1
traceEvent: Processing EV_ABS ABS_MT_TOUCH_MAJOR 0
traceEvent: Processing EV_SYN SYN_MT_REPORT 0
The log shows "Processing EV_ABS ABS_MT_TRACKING_ID 1" twice and does not show "EV_SYN SYN_REPORT 0" as it should.
traceEvent: Read EV_ABS ABS_MT_TRACKING_ID 1
traceEvent: Read EV_ABS ABS_MT_TOUCH_MAJOR 0
EV_SYN SYN_MT_REPORT 0
traceEvent: Read EV_SYN SYN_MT_REPORT 0
0.002 TestLog: TestTouchDevice: sync
EV_SYN SYN_REPORT 0
traceEvent: Read EV_SYN SYN_REPORT 0
traceEvent: Processing EV_ABS ABS_MT_TRACKING_ID 1
traceEvent: Processing EV_ABS ABS_MT_TRACKING_ID 1
traceEvent: Processing EV_ABS ABS_MT_TOUCH_MAJOR 0
traceEvent: Processing EV_SYN SYN_MT_REPORT 0
The log shows "Processing EV_ABS ABS_MT_TRACKING_ID 1" twice and does not show "EV_SYN SYN_REPORT 0" as it should.