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 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 Status in qtsystems-opensource-src package in Ubuntu: Confirmed Bug description: I’ve prepared a branch of webbrowser-app that makes use of the latest qml-module-qtsysteminfo for input device detection (https://code.launchpad.net/~osomon/webbrowser-app/use- qtsystems/+merge/309667), and when I test it on arale, I’m seeing the following error in the logs when connecting a bluetooth keyboard/mouse combo to the device: QObject: Cannot create children for a parent that is in a different thread. (Parent is QInputInfoManagerMir(0xaa09a6ac), parent's thread is QThread(0x1fba0b8), current thread is QThread(0xb08612d8) This looks like a threading issue in the implementation of the Mir backend for InputInfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtsystems-opensource-src/+bug/1638517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
