touch-packages team mailing list archive

[Daniel van Vugt <daniel.van.vugt@xxxxxxxxxxxxx>]

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.

** Changed in: mir (Ubuntu)
       Status: New => Invalid

-- 
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 package in Ubuntu:
  Invalid
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/ubuntu/+source/mir/+bug/1488417/+subscriptions