summaryrefslogtreecommitdiffstats
path: root/config.tests/dmabuf_client_buffer/main.cpp
diff options
context:
space:
mode:
authorJohan Klokkhammer Helsing <johan.helsing@qt.io>2019-08-26 14:55:16 +0200
committerJohan Klokkhammer Helsing <johan.helsing@qt.io>2019-09-20 16:09:48 +0200
commitd8c19df22a1ff6ee40373a96fa12183acfc1b452 (patch)
tree46aa62586394844f079512a371d7dd675030cb21 /config.tests/dmabuf_client_buffer/main.cpp
parent694c96254b79cbe1c45ee6bafedf9649ee88abbc (diff)
Client: Test that wl_touch.up events don't split touch framesv5.14.0-alpha1
We have a workaround for Weston not sending wl_touch.frame events after the last wl_touch.up event. It calls Touch::touch_frame to generate a fake event. The problem, however, is that it used to erroneously do this on wl_touch.up events even when it was not for the last touch point. This in turn, lead to extra frame events being inserted in the middle of a touch sequence, effectively splitting up one touch frame into multiple. Accumulated touch state would be handled prematurely, preventing wl_touch.cancel from working correctly for instance. This tests that we've stopped doing that. Change-Id: Ic545bbb18c23b827e5fa07a642a374094d720dae Reviewed-by: Paul Olav Tvete <paul.tvete@qt.io>
Diffstat (limited to 'config.tests/dmabuf_client_buffer/main.cpp')
0 files changed, 0 insertions, 0 deletions