> AFAIK the only thing stopping us from using Mir's native input coordinates > was the inability to implement barriers/edge resistance in places.
We had other use-cases where unity8 having control over mouse position was useful. One example coming to mind is phone docked to an external display, we wanted to limit the cursor to the external display only. And we had a few other pie-in-the-sky design ideas which would be much easier if unity8 had cursor control. I still don't see why Mir can't just let Unity8 (a nested) position the cursor (like it could, if it were a host server)! And absolute vs relative. If we're doing it wrong, we can fix it. -- 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/1670670 Title: Unity8 pointer does not stay in sync with Qemu VM tablet input Status in Canonical System Image: Confirmed Status in mir package in Ubuntu: Invalid Status in qtmir package in Ubuntu: Confirmed Status in unity8 package in Ubuntu: Confirmed Bug description: Each time you login, or come back from the lock screen, you need to "recalibrate" the pointer by carefully moving the pointer into each corner. Contrast this with unity7, where the absolute position of the virtual tablet pointer is tracked, and sync is never lost. To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1670670/+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