ubuntu-sdk-bugs team mailing list archive

[Olivier Tilloy <olivier.tilloy@xxxxxxxxxxxxx>]

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
SDK bug tracking, 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