@Zanetti > Here's a way to easily reproduce it with the dash to verify if this issue is > fixed: > [...]
Thanks for that test case! Very useful. That's another issue, which lp:~dandrader/qtmir/missingTouchEnd- lp1295623 doesn't fix. I was hoping to deal with it in another bug report but we can keep using this one since to the user it's hard to distinguish between the two. So, those are the problems: 1 - unity8 not receiving a touch end from Mir (or lower, like the evedev device) and thus having its mouse event emulation getting stuck 2 - A MirSurfaceItem inside unity8's QML scene not receiving a touch end, and thus leaving the mouse event emulation of the corresponding Qt client app stuck (like unity8-dash). So lp:~dandrader/qtmir/missingTouchEnd-lp1295623 fixes item 1. Now I'm working on a fix/workaround for item 2. Item 2 does look like a Qt bug (although some might claim we're using its API wrongly). It happens when you disable an Item while it's owning a touch point, which causes QQuickWindow's event delivery to stop sending touch events for that Item (which is ok). But it will never get further updates for that touch point even when reenabled. Meaning it will never get a TouchEnd for that touch. When you tap on it again it receives a whole new TouchBegin like if the previous touch point, whose end is still pending, never existed. So, when you disable an Item that owns a touch point I think QQuickWindow should synthesize a TouchEnd for that disabled Item. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1295623 Title: Sometimes input breaks and only edges are responsive To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1295623/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
