I expect we will make it a flag that clients can toggle in future:
"Resample input for me" = {yes,no}
So if anyone thinks their toolkit can do better resampling, they will be
able to.
On 15/09/14 17:59, Gerry Boland wrote:
Yep, I was aware of this, so was happy that you guys landed the touch
processing stuff. I hadn't noticed that Qt landed this change though, nice to
know.
-G
On 15/09/14 03:20, Daniel van Vugt wrote:
How very timely. That's exactly the "touch responsiveness" enhancement
that we just released in Mir 0.7.0 on 1 September :)
And in fact, the scenario discussed in the blog is exactly what the new
test case "rendering_does_not_lag_behind_input" covers:
http://bazaar.launchpad.net/~mir-team/mir/development-branch/revision/1875/tests/unit-tests/client/input/test_android_input_receiver.cpp
Of course, now we're used to it already it's hard to remember that touch
was more laggy before Mir 0.7. But there are other improvements
elsewhere in Mir we can still make to reduce that further in future...
On 13/09/14 13:35, Christopher James Halse Rogers wrote:
I thought Qt was already smart enough to do this. Clearly not; thanks
Jolla!
http://blog.rburchell.com/2014/09/profiling-is-not-understanding.html
--
Mir-devel mailing list
Mir-devel@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/mir-devel
