Details
-
Bug
-
Resolution: Done
-
P1: Critical
-
6.2.1, 6.2.2
-
None
-
Windows 10 , MSVC 2019, Qt Creator 5.0.3, Qt 6.2.1
-
-
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)
Description
The touch points coordinates received by controls doesn't take into account the Device Pixel Ratio, the result is that, when the device pixel ratio is different than 1, a slider follows the input coordinates when using the mouse, but doesn't when using touch . Same problem whith Flickable.
No problem with Qt 5.15
Attachments
Issue Links
- relates to
-
QTBUG-98543 Invalid updates of contentY of Flickable on touch screen
- Closed
-
QTBUG-97185 Quick DragHandler Reporting Wrong Coordinates using TouchScreen Input
- Closed
For Gerrit Dashboard: QTBUG-98486 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
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 |