[Wayland-bugs] [Bug 83383] fail to receive touch_frame after final touch_up (Qt)
https://bugs.freedesktop.org/show_bug.cgi?id=83383 GitLab Migration User changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |MOVED --- Comment #4 from GitLab Migration User --- -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/44. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83383] fail to receive touch_frame after final touch_up (Qt)
https://bugs.freedesktop.org/show_bug.cgi?id=83383 Daniel Stone changed: What|Removed |Added Component|wayland |weston -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83383] fail to receive touch_frame after final touch_up (Qt)
https://bugs.freedesktop.org/show_bug.cgi?id=83383 --- Comment #3 from Johan Helsing --- We ended up doing a workaround for it in Qt: https://codereview.qt-project.org/#/c/93572/ Since we're not sort of breaking the protocol, I created: https://bugreports.qt.io/browse/QTBUG-66563 I'm not aware of any problems caused by the workaround, except that it caused one of our tests to be flaky. That can be worked around, too, though. -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list wayland-bugs@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83383] fail to receive touch_frame after final touch_up (Qt)
https://bugs.freedesktop.org/show_bug.cgi?id=83383 --- Comment #2 from Shawn Rutledge --- I should rather say that the Qt touch handling strategy is to accumulate touchpoints and then handle them when we receive a touch_frame, and that in turn is because of the architecture that multiple touch points are grouped into a single QTouchEvent. We've been thinking of having separate events for each touch point movement in Qt 6 (can't do such big changes in Qt 5). This would help to facilitate a better event inheritance tree so that handling of mouse, touch and tablet events could be unified in some elements that don't care much about the differences between them (if there is to be a QPointingEvent base class from which QTouchEvent inherits, it should have only a single pair of coordinates). And multiple mice could be treated much like multiple fingers (except that multiple mice tends to imply multiple users, so maybe we need a "seat" concept like wayland has). If we did that, then maybe it would be appropriate to ignore the touch_frame entirely, which might improve reliability. But for now we depend on it, because we generally don't send a QTouchEvent until all the touch points have been updated (except for this latest workaround when all touch points are released). -- You are receiving this mail because: You are the assignee for the bug. ___ Wayland-bugs mailing list Wayland-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
[Wayland-bugs] [Bug 83383] fail to receive touch_frame after final touch_up (Qt)
https://bugs.freedesktop.org/show_bug.cgi?id=83383 --- Comment #1 from Shawn Rutledge --- related Qt bug: https://bugreports.qt-project.org/browse/QTBUG-36602 -- You are receiving this mail because: You are the assignee for the bug. ___ Wayland-bugs mailing list Wayland-bugs@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-bugs
