From e33fd7157f293e3f894b174b8bd3134bfd51685b Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Mon, 6 Aug 2018 14:06:48 +1000 Subject: [PATCH] tools: record: don't bother setting last_ms to 0 on the first event The first event we receive is set to a 0ms offset anyway. Setting last_ms to 0 on the first event means the first two events have +0ms offset printed to the log. Skip it, so the second event has the right offset. This is human-readable data only, no effect on the recording file itself. Signed-off-by: Peter Hutterer --- tools/libinput-record.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/tools/libinput-record.c b/tools/libinput-record.c index 169947df..0f1cb174 100644 --- a/tools/libinput-record.c +++ b/tools/libinput-record.c @@ -215,8 +215,6 @@ print_evdev_event(struct record_context *ctx, struct input_event *ev) unsigned long time, dt; time = us2ms(tv2us(&ev->time)); - if (last_ms == 0) - last_ms = time; dt = time - last_ms; last_ms = time;