Priority: P1: Critical
Affects Version/s: 6.2.1
Component/s: Quick: Mouse Touch and Tablet input
Environment:Windows 10, Dell XPS 15 7590
Commits:d08038ba70 (qt/qtdeclarative/dev) d08038ba70 (qt/tqtc-qtdeclarative/dev) ee68d19b1d (qt/qtdeclarative/6.3) ee68d19b1d (qt/tqtc-qtdeclarative/6.3) cf39c6e28d (qt/qtdeclarative/6.2) cf39c6e28d (qt/tqtc-qtdeclarative/6.2) cf39c6e28d (qt/qtdeclarative/6.2.4)
Flickable has a problem with updating of contentY while moving (no flicking) on touch screen with touch (mouse is OK). The problem is on Windows, I tested it with Qt 6.2.1 for Android and there it works fine. This must be a regression, because on Windows with Qt 5.15.0 the problem does not occur either.
I have attached a sample application showing the problem (test22.zip):
To reproduce the problem you have to touch the flickable somewhere in the middle and slowly move your finger towards the top of the window. You may then notice strange content jumping instead of moving smoothly. Some of the contentY values appear to be totally incorrect.
Below are the logs from the application:
- For Qt 6.2.1 (incorrect - for moving from bottom to top there should not be any negative values):
- For Qt 5.15.0 (correct):
|For Gerrit Dashboard: QTBUG-98543|
|383720,11||Detach QEventPoint instances during touch compression; test & docs||dev||qt/qtdeclarative||Status: MERGED||+2||0|
|393849,2||Detach QEventPoint instances during touch compression; test & docs||6.3||qt/qtdeclarative||Status: MERGED||+2||0|
|393850,3||Detach QEventPoint instances during touch compression; test & docs||6.2||qt/qtdeclarative||Status: MERGED||+2||0|