Ah yes the android input transport is biting us again. We are still bound to the limitation of that encoding. That encoding means - only one down/up touch id per event. No matter what libinput reads or qtmir sanitizes.. , as long as the transport from server to nested server or from nested server to client chops of the information of every additional down or up the gesture will break. I will keep the fix close to the encoding so we can get rid of it easier...
-- 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/1531517 Title: [regression] pinch to zoom not working reliably Status in Canonical System Image: Confirmed Status in Mir: Confirmed Status in Mir 0.18 series: Confirmed Status in mir package in Ubuntu: Confirmed Status in qtmir package in Ubuntu: Won't Fix Bug description: in the last few days (using rc-proposed 221 on krillin) pinch to zoom gestures do not work reliably anymore. Appears to be system wide as there have been reports in the follow apps that all use PinchArea from QML: - Camera: pinch to zoom in viewfinder stops working, pinch to zoom in Photo Roll to zoom a photo stops working - Gallery: open a photo and pinch to zoom doesn't work - Webbrowser: pinch to zoom on a web page not working Could be mir/qtmir related To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1531517/+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
