More accurate representation of what we actually want to do. Plus it avoids weird test case failures in semi-mt where we always pick the t/l and b/r touches for the bounding box. That is the proper behavior for semi-mt, but it's not for the tests where we expect simultaneous finger movement.
Signed-off-by: Peter Hutterer <[email protected]> --- test/litest.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/test/litest.c b/test/litest.c index cc348e9..1551dc7 100644 --- a/test/litest.c +++ b/test/litest.c @@ -1500,18 +1500,22 @@ litest_touch_move_two_touches(struct litest_device *d, int steps, int sleep_ms) { for (int i = 0; i < steps - 1; i++) { + litest_push_event_frame(d); litest_touch_move(d, 0, x0 + dx / steps * i, y0 + dy / steps * i); litest_touch_move(d, 1, x1 + dx / steps * i, y1 + dy / steps * i); + litest_pop_event_frame(d); if (sleep_ms) { libinput_dispatch(d->libinput); msleep(sleep_ms); } libinput_dispatch(d->libinput); } + litest_push_event_frame(d); litest_touch_move(d, 0, x0 + dx, y0 + dy); litest_touch_move(d, 1, x1 + dx, y1 + dy); + litest_pop_event_frame(d); } void -- 2.5.0 _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
