Public bug reported: In testing a unity8 branch that wanted to make use of QInputEvent timestamps, I discovered that they seem a bit unreliable in Mir (testing on a mako).
I often would get 0. And the timestamps themselves would be all over the place, seemingly overflowing. See https://pastebin.canonical.com/142915/ for a log (the MIKE lines indicate true/false for whether the event is an autorepeat event and then the next number is the Qt timestamp). Might be an issue with stuffing int64 into a ulong? Or might be something else random. I'm trying to get a tighter test case. ** Affects: qtmir (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1511076 Title: Qt timestamps seem off To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtmir/+bug/1511076/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
