[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2017-01-13 Thread Lorn Potter
** Changed in: qtsystems-opensource-src (Ubuntu) Assignee: Lorn Potter (lorn-potter) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1638

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-30 Thread Olivier Tilloy
Note that I’m affected by another issue that prevents me from making use of InputDeviceModel in QML: bug #1646080. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-29 Thread Olivier Tilloy
How about not passing any argument to the signal emission? AFAIK, a lot of Qt *Changed signals don’t take any argument, so that would be in line with existing code. Of course we’d need to verify that by the time the signal is emitted the row count has actually changed. -- You received this bug no

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-29 Thread Lorn Potter
I seem to remember @timo-jyrinki suggesting the 'devices' name at review time, so I must have not changed the base class. Not sure which one makes more sense. Suggestions? Opinions?? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribe

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Olivier Tilloy
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 QtSyste

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter
@osomon The reason you are seeing this not work correctly, is because the value for countChanged signal is named 'devices' in the declarative class, and not 'count' like what is in the base class and that you are using in your qml example. This should probably get changed in the declarative class

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter
Got this working on my laptop w/ unity8... Except it does work, still see that thread message, except the count is opposite of what it should be. When I disconnect the keyboard (usb as well as bt) it says count: 2, and when I connect it count: 1 When I first run the test qml, it reports count: 0

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter
I can reproduce this on turbo. Does not happen when running the inputinfo console app in qtsystem examples. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/16

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Olivier Tilloy
I don’t know where that code lives. https://code.launchpad.net/ubuntu/+source/qtsystems-opensource-src/ doesn’t have the latest changes it seems. Timo would know. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-open

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter
I meant latest repo for qtsystems-opensource-src. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1638517 Title: Mir-backed InputDeviceModel doesn’t work o

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Olivier Tilloy
@Lorn: no need for webbrowser-app, the issue can be reliably reproduced with the standalone QML example in comment #1. I just tested on arale with the latest rc-proposed image, saved the example as /tmp/test.qml and ran it like so: phablet@ubuntu-phablet:/tmp$ qmlscene --desktop_file_hint=unity8

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-28 Thread Lorn Potter
where is the latest bzr repo? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtsystems-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1638517 Title: Mir-backed InputDeviceModel doesn’t work on touch device Stat

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-27 Thread Lorn Potter
How can I reproduce this? When I try that qml on qmlscene on my lenovo yoga running unity8, I get a seg fault in libunubtu_application_api_desktop_mirclient.so.3.0.0 ** Changed in: qtsystems-opensource-src (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-04 Thread Timo Jyrinki
I tested this in bug #1536669 on krillin and Unity 8 desktop on Chromebook, and it worked fine with the example apps, the QML of which called: InputDeviceModel { id: deviceModel filter: InputInfo.Keyboard | InputInfo.Mouse | InputInfo.TouchScreen onCountChanged: {

[Touch-packages] [Bug 1638517] Re: Mir-backed InputDeviceModel doesn’t work on touch device

2016-11-02 Thread Olivier Tilloy
I can reliably reproduce the issue with the following standalone example: import QtQuick 2.4 import QtSystemInfo 5.5 Item { InputDeviceModel { filter: InputInfo.Keyboard onCountChanged: console.log("keyboard count:", count) } } -- You received this bug notification because you are a