| Thread Previous • Date Previous • Date Next • Thread Next |
This bug was fixed in the package qtubuntu -
0.60+14.10.20140808.1-0ubuntu1
---------------
qtubuntu (0.60+14.10.20140808.1-0ubuntu1) utopic; urgency=low
[ Gerry Boland ]
* Workaround for bug 1346633 broke QGuiApplication::topLevelWindows(),
perform a different workaround. This workaround guesses the window
geometry relative to the screen (mainly setting y=panelHeight),
defining it using QPlatformWindow::setGeometry and then Qt uses it
to calculate mapToGlobal internally (LP: #1351024, #1346633)
-- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx> Fri, 08 Aug 2014 14:10:40 +0000
** Changed in: qtubuntu (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtubuntu in Ubuntu.
https://bugs.launchpad.net/bugs/1346633
Title:
[enhancement] Autopilot testing needs to know screen coordinates of
widgets on screen
Status in Autopilot:
New
Status in Mir:
New
Status in Qt integration with the Mir display server:
New
Status in “qtubuntu” package in Ubuntu:
Fix Released
Bug description:
On phablet devices, Autopilot needs to determine the absolute
coordinates of any item on screen, in order to generate input events
to interact with those items.
Most toolkits give AP the ability to calculate the coordinates of an
item inside the surface, i.e. relative to the surface top-left corner,
and then obtain the position of the window from the display server
(X11 usually) to calculate the absolute position.
However Mir does not have an API to let its clients find the surface
position relative to the screen. There is also a desire from the Mir
team not to supply this information.
We need to discuss how to solve this problem in a way everyone is
happy
To manage notifications about this bug go to:
https://bugs.launchpad.net/autopilot/+bug/1346633/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
