Now we know what the problem is, and it will be gone once qtmir+unity8
start using one surface per display instead of cloning displays as it's
currently happening.
** Changed in: mir (Ubuntu)
Status: In Progress => New
** Changed in: qtmir (Ubuntu)
Status: Invalid => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1488417
Title:
nexus4 window mode mouse motion bounded incorrectly with external
monitor
Status in canonical-pocket-desktop:
New
Status in Mir:
New
Status in mir package in Ubuntu:
New
Status in qtmir package in Ubuntu:
New
Bug description:
when connecting a monitor to the Nexus4 during windowed mode, the
device is put into landscape mode. the mouse motion appears to not
have followed the orientation and is bounded by roughly portrait width
instead of landscape width
The problem is that when unity8 configures cloning, it picks the intersection
of all displays. While the input subsystem uses the bounding rectangle of all
displays. Thus it allows the cursor to move around in (1200x1920) while the
only surface is 1080x1920. So there is a dead zone between the display extent
and the surface extent. When the cursor hits that area the
SurfaceInputDispatcher has no surface underneath, so it decides to not send any
further mouse input to Unity8.
We can fix that by extending the behaviour of display_input_region.cpp
to use the intersection of displays when necessary.
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-pocket-desktop/+bug/1488417/+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
