Aha! Confirmed on arale with a USB mouse and mir-demos.
Relative motion events usually work continuously, and come in even after
the cursor hits the screen boundary. However Mir stops sending relative
motion events if you've rotated the screen (touch+volume key in
mir_proving_server) and the cursor happens to be outside of the original
non-rotated dimensions. That's a Mir bug.
** Changed in: mir (Ubuntu)
Status: Incomplete => Confirmed
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New => Confirmed
--
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
Status in Mir:
Incomplete
Status in mir package in Ubuntu:
Incomplete
Status in qtmir package in Ubuntu:
Opinion
Status in unity8 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+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
