Qt timestamps seem off
Bug #1511076 reported by
Michael Terry
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical System Image |
Fix Released
|
High
|
Unassigned | ||
| qtmir (Ubuntu) |
Fix Released
|
High
|
Michael Terry | ||
Bug Description
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:/
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.
Related branches
lp:~mterry/qtmir/ms-compressed-timestamps
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
- Mir development team: Pending requested
-
Diff: 74 lines (+21/-6)3 files modifiedsrc/common/timestamp_impl.h (+3/-3)
tests/mirserver/QtEventFeeder/qteventfeeder_test.cpp (+15/-0)
tests/modules/General/timestamp_test.cpp (+3/-3)
lp:~unity-team/qtmir/1510571.ms-timestamp-compression
- Gerry Boland (community): Approve
- PS Jenkins bot (community): Needs Fixing (continuous-integration)
-
Diff: 265 lines (+62/-42)5 files modifiedsrc/common/timestamp_impl.h (+6/-5)
src/modules/Unity/Application/mirsurface.cpp (+4/-4)
src/platforms/mirserver/qteventfeeder.cpp (+11/-13)
tests/mirserver/QtEventFeeder/qteventfeeder_test.cpp (+15/-0)
tests/modules/General/timestamp_test.cpp (+26/-20)
| Changed in qtmir (Ubuntu): | |
| status: | New → In Progress |
| assignee: | nobody → Michael Terry (mterry) |
| importance: | Undecided → High |
| Changed in canonical-devices-system-image: | |
| importance: | Undecided → High |
| status: | New → Fix Committed |
| milestone: | none → ww46-2015 |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #1 |
| Changed in qtmir (Ubuntu): | |
| status: | In Progress → Fix Released |
| Changed in canonical-devices-system-image: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
This bug was fixed in the package qtmir - 0.4.6+16.
---------------
qtmir (0.4.6+
[ Alan Griffiths ]
* Test harness for MirWindowManager (in preparation for more
intelligent window management)
[ CI Train Bot ]
* New rebuild forced.
[ Michael Terry ]
* Support new isTouchApp property to ApplicationInfo
lifecycle policy logic out of qtmir.
[ Michał Sawicz ]
* Clean up packaging and fix autopkgtest on armhf
[ Nick Dedekind ]
* Hand Qt millisecond timestamps rather than nanosecond. (LP:
#1510571, #1511076, #1511711)
* Support server->client visibility change to stop rendering
(lp:#1475678) (LP: #1475678)
-- Michał Sawicz <email address hidden> Mon, 02 Nov 2015 11:22:29 +0000