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