Nice catch Lorn! This is a nasty one. I would have expected that the
value of the count property would be updated *before* the countChanged
signal is emitted, regardless of the name of the parameter of the
signal.
So I just verified that if I do that, this works:
import QtQuick 2.4
import QtSystemInfo 5.5
Item {
InputDeviceModel {
filter: InputInfo.Keyboard
onCountChanged: console.log("keyboard count:", devices)
}
}
However I’m wary of using that just yet, in case you decide to change
the name of the parameter to 'count', my code would break. Please let me
know if you plan to do so, and I’ll just hold off.
Also, the warning about object ownership and threads is still present. I
think it should be investigated, as it’s usually a good indicator that
something is not architected correctly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638517
Title:
Mir-backed InputDeviceModel doesn’t work on touch device
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
