Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.6.1
-
None
-
ec4368adb (dev), 58c40a939 (6.7), 5bd416a25 (6.6)
Description
The behavior for boundsMovement has been adapted to be more unique between wheel scrolling or touch based interaction.
In parts the "wheel feel" for flickables has been improved, but what's strange, is that some wheel clicks lead to a maximum overshoot of the flickable contents, so that there's a completely empty window. See video. Left side Qt 6.6.1, right side Qt 6.5.3.
I'd expect it to overshoot with the mouse wheel, but have a higher "resistance", so that it's not possible for the screen to become completely white.
Attachments
Issue Links
- is duplicated by
-
QTBUG-120179 [REG 6.5-6.6] Flickable overshoot is crazy again with mouse wheel
- Closed
- relates to
-
QTBUG-114607 Flickable.StopAtBounds not working anymore with a wheel
- Closed
For Gerrit Dashboard: QTBUG-121349 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
540680,5 | Flickable mouse wheel: overshoot less, and return to bounds sooner | dev | qt/qtdeclarative | Status: MERGED | +2 | 0 |
541435,2 | Flickable mouse wheel: overshoot less, and return to bounds sooner | 6.7 | qt/qtdeclarative | Status: MERGED | +2 | 0 |
541490,2 | Flickable mouse wheel: overshoot less, and return to bounds sooner | 6.6 | qt/qtdeclarative | Status: MERGED | +2 | 0 |