Commit e33fd715 authored by Peter Hutterer's avatar Peter Hutterer
Browse files

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's avatarPeter Hutterer <peter.hutterer@who-t.net>
parent cf808a40
Pipeline #2967 failed with stages
in 64 minutes and 39 seconds
......@@ -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;
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment