Comment 6 for bug 1488417
Revision history for this message
| Daniel van Vugt (vanvugt) wrote Re: nexus4 window mode mouse motion bounded incorrectly | #6 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
OK, I can see one problem already. While Unity8 does its own screen rotation without notifying Mir, Mir cannot do anything to help it update the cursor bounds. Because Unity8 is not telling Mir that the display has rotated, Mir will keep the old cursor bounds...
Portrait:
$ mirout /var/run/mir_socket
Connected to server: /var/run/mir_socket
Card 0: Max 2 simultaneous outputs
Output 0: Card 0, LVDS, connected, 768x1280+0+0, used, on, 61mm x 102mm (4.7"), normal
768x1280 60.00*+
Output 1: Card 0, DisplayPort, disconnected
Landscape (incorrectly shows orientation still "normal"):
$ mirout /var/run/mir_socket
Connected to server: /var/run/mir_socket
Card 0: Max 2 simultaneous outputs
Output 0: Card 0, LVDS, connected, 768x1280+0+0, used, on, 61mm x 102mm (4.7"), normal
768x1280 60.00*+
Output 1: Card 0, DisplayPort, disconnected
So if Unity8 is going to keep doing rotation independently of Mir, it either needs to find a way to update the Mir display config without making Mir actually apply that display config, or Unity8 do mouse movement entirely within itself using relative motion.