Invalid for Mir because the enhancement Gerry mentioned is covered in bug 1600220 instead.
If Unity8 used the absolute pointer coordinates that USC gives it then we wouldn't have a problem here. If Unity8 doesn't want to use those all the time then we will need to work out a compromise that makes events from Qemu's mouse/tablet hybrid more obviously absolute (like touches are) so that clients (which U8 is one) know that relative motion from that device is useless. In Qemu you can move the cursor off the right edge of the window, move it around the Qemu window and make it appear on some other edge. It would be messy at least to try and communicate that using relative motion data. If we really want to do that then sure this is a Mir bug, but I don't think we want to do that. Useful links: https://bugs.launchpad.net/mir/+bugs?field.tag=wacom https://bugs.launchpad.net/mir/+bugs?field.tag=cursor -- 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: Invalid 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 : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
