Skip to content

tools: record: don't bother setting last_ms to 0 on the first event

Peter Hutterer requested to merge whot/libinput:wip/libinput-record-initial-offset into master

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.

Merge request reports