aboutsummaryrefslogtreecommitdiffstats
path: root/src/qml/jsruntime/qv4arraybuffer.cpp
diff options
context:
space:
mode:
authorShawn Rutledge <shawn.rutledge@qt.io>2022-07-07 22:23:37 +0200
committerShawn Rutledge <shawn.rutledge@qt.io>2022-08-25 23:57:11 +0000
commit79893e1773be9d04208243cb88c1daf793d830a4 (patch)
treec1cdddfe3a2a7e36be791e843c6fc9aa39525001 /src/qml/jsruntime/qv4arraybuffer.cpp
parent68dc224920ddf3aeb67a87d9b983107a88fd7974 (diff)
Ensure that multiple HoverHandlers can react to multiple device types
1c44804600ad3dbeb60d1f5209ce9cf937d30ab3 had some known incompleteness in QQuickItemPrivate::effectiveCursorHandler because it couldn't be finished in Qt 5; but HoverHandlers with different acceptedDevices and acceptedPointerTypes were working together in Qt 6.0 and 6.1 to an extent. Perhaps for this case it helped that HoverHandlers got passive grabs, but we stopped that in bbcc2657fa0dbf715e6db7d675662e4be94a1e04. So now, as with mouse events, we need to ensure that when a HoverHandler detects a particular stylus device in a QTabletEvent and chooses a different cursor, it is applied to the window. At this time, since QQuickDeliveryAgentPrivate::deliverHoverEvent() sends a synth-mouse event, it's not suitable for tablet hover; so we depend on correct implementation of allPointsGrabbed() to ensure that QQuickDeliveryAgentPrivate::deliverUpdatedPoints() will visit all the HoverHandlers, in this case only. Pick-to: 6.3 6.4 Fixes: QTBUG-101932 Change-Id: Ia8f31610e9252825afc7151be58765ac5217b0e8 Reviewed-by: Doris Verria <doris.verria@qt.io>
Diffstat (limited to 'src/qml/jsruntime/qv4arraybuffer.cpp')
0 files changed, 0 insertions, 0 deletions