diff options
| author | Shawn Rutledge <shawn.rutledge@qt.io> | 2023-06-28 18:41:44 +0200 |
|---|---|---|
| committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2023-06-29 09:34:19 +0200 |
| commit | 204720cb55219976ea509704acff066edff0bbbc (patch) | |
| tree | ab684c8759926a2675ba0dfa5cf91002fd98e4c5 /src/quick/doc/snippets/qml/loader/KeyReader.qml | |
| parent | 6362da587017a022df88e5e473b2115f0d17092c (diff) | |
Stabilize tst_TouchMouse::hoverEnabled; add cat. logging
Behavior has changed since fd70c80fe1cac83776cc4730555c8e3dea930c1c
Particularly, the "hoverID" concept from
bbcc2657fa0dbf715e6db7d675662e4be94a1e04 basically ensures that items
that no longer contain the current position are no longer hovered.
The current position might come from an actual event, or from
QQuickDeliveryAgentPrivate::flushFrameSynchronousEvents() which uses
lastMousePosition. So currently we can't have mouseArea1 hovered because
of a previous mouse move and simultaneously hover mouseArea2 because of
the most-recent touch tap. lastMousePosition can in turn get updated in
various ways; a mouse event synthesized from touch is one of them.
Pick-to: 6.5 6.6
Task-number: QTBUG-40856
Task-number: QTBUG-86729
Change-Id: I4e70b67813a58de973b2be46a03312417f2da32e
Reviewed-by: Qt CI Bot <qt_ci_bot@qt-project.org>
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Diffstat (limited to 'src/quick/doc/snippets/qml/loader/KeyReader.qml')
0 files changed, 0 insertions, 0 deletions