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 <peter.hutterer@who-t.net>
This commit is contained in:
Peter Hutterer 2018-08-06 14:06:48 +10:00
parent cf808a408f
commit e33fd7157f

View file

@ -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;