autopilot-qt uses the Qt API to determine the coordinates of each widget in screen-space. Specifically, it uses QWidget::mapToGlobal to do the translation.
To my mind, since that API exists, and mir is supposed to support the Qt framework, the call should continue to work.
Gerry and I discussed a few other options, including exposing a dbus interface from unity8 that does the translation, but nothing I could come up with would be as straight forward and as clean as having the existing Qt API "just work".
It's also worth remembering that, while the current problem is with autopilot-qt, this is a public part of the Qt API, so it's possible that other applications in the future will be similarly broken by this change.
A small addendum to the above:
autopilot-qt uses the Qt API to determine the coordinates of each widget in screen-space. Specifically, it uses QWidget: :mapToGlobal to do the translation.
To my mind, since that API exists, and mir is supposed to support the Qt framework, the call should continue to work.
Gerry and I discussed a few other options, including exposing a dbus interface from unity8 that does the translation, but nothing I could come up with would be as straight forward and as clean as having the existing Qt API "just work".
It's also worth remembering that, while the current problem is with autopilot-qt, this is a public part of the Qt API, so it's possible that other applications in the future will be similarly broken by this change.
Cheers,