Subject: Qt Quick, input processing, and blogposts

From: Christopher James Halse Rogers <[email-masked]>
Date: Sat, 13 Sep 2014 15:35:00 +1000

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

---

From: Daniel van Vugt <[email-masked]>
Date: Mon, 15 Sep 2014 10:20:28 +0800

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...

---

From: Gerry Boland <[email-masked]>
Date: Mon, 15 Sep 2014 10:59:44 +0100

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

---

From: Daniel van Vugt <[email-masked]>
Date: Tue, 16 Sep 2014 09:26:07 +0800

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.