[17:02] <dandrader> anpok, mir input event timestamps: does mir generates them from scratch or do they come from a lower layer?
[17:19] <bschaefer> dandrader, in platforms/evdev/libinput_devices.cpp
[17:19] <bschaefer> (say for keyboard: libinput_event_keyboard_get_time_usec)
[17:19] <bschaefer> soo it seems like it comes from libinput based on the event being translated
[17:20] <dandrader> bschaefer, ok, thanks. and yeah, I'm interested in kbd timestamps more specifically
[17:21] <bschaefer> should be this function: mir::EventUPtr mie::LibInputDevice::convert_event(libinput_event_keyboard* keyboard)
[17:21] <bschaefer> which sound propagate through all the nested bits into qtmir
[17:21] <dandrader> bschaefer, so to synthesize a mir event I guess I will have to add elapsed time to some known event timestamp
[17:22] <bschaefer> hmm yeah, umm let me check what evdev does
[17:24] <bschaefer> as we use timestamps to check which event was last (for surface raise... and something else now)
[17:30] <bschaefer> looks like it uses a timerfd_create(CLOCK_MONOTONIC, TFD_CLOEXEC | TFD_NONBLOCK);
[17:31] <bschaefer> (though not sure how much help that is when its past mir :)