Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
6.0.0
-
None
-
d7623d79ef4bc9533fced027bf1d173d68b4eba6 (qt/qtdeclarative/dev)
Description
This is one big reason for the event refactoring: even though Flickable doesn't explicitly deal with touch events, it should be able to replay them to delegates that do care about receiving actual touches instead of fake mousepresses. (Further, Flickable should be able to flick via touch, because its event handling code can probably become agnostic about the device the event comes from: touch and mouse events begin to look more alike. But we'll see about that.)
After https://codereview.qt-project.org/c/qt/qtdeclarative/+/305381 the old hacks are somehow broken again, and it's not worth my time to fix the old hacks again when we want to do it this way instead.
As tests get disabled along the way (such as tst_TouchMouse::buttonOnDelayedPressFlickable(release before press delay is over) ) they should be listed here, and then this bug can be marked fixed when the tests are passing again.
Attachments
Issue Links
- resulted from
-
QTBUG-61144 Taps don't occur for Buttons in ListView with pressDelay set
- Closed
-
QTBUG-72173 Refactor the QEvent hierarchy to make input events more like QQuickPointerEvents in Qt 6
- Closed
- resulted in
-
QTBUG-88170 tst_QQuickDrawer::Basic::slider fails after making Flickable handle touch events directly
- Closed