diff options
| author | Peter Hutterer <peter.hutterer@who-t.net> | 2016-01-22 11:36:40 +1000 |
|---|---|---|
| committer | Peter Hutterer <peter.hutterer@who-t.net> | 2016-01-22 11:37:51 +1000 |
| commit | d19307f20d536cb7a5a402e0387a1aeb81ecec89 (patch) | |
| tree | 3ef1e05471bb662106fa5e8d4c0074faa69c4d72 | |
| parent | 14baf58e3746bc07c1c290fb673b5723d45eb077 (diff) | |
| download | libinput-d19307f20d536cb7a5a402e0387a1aeb81ecec89.tar.gz | |
test: when moving 2 fingers, move them in the same frame
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 <peter.hutterer@who-t.net>
Reviewed-by: Hans de Goede <hdegoede@redhat.com>
| -rw-r--r-- | test/litest.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/test/litest.c b/test/litest.c index cc348e9e..1551dc74 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 |