diff options
author | Shawn Rutledge <shawn.rutledge@qt.io> | 2020-09-16 16:37:25 +0200 |
---|---|---|
committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2020-09-17 04:21:33 +0200 |
commit | b850322147250a1bd35d5c63e958dec161284244 (patch) | |
tree | a886191f77ac280319684e83500f4e1827398d9f /tests/auto | |
parent | 8932e80d0c8879a1e720fef825ed0d9c4e384a01 (diff) |
QPointingDevPriv::setExclusiveGrabber: emit grabChanged with point found
...not with the given point. Since QEventPoint has a constructor that
takes an id, it's possible to write something like
pointerEvent->setExclusiveGrabber(pointId, object)
which will construct a QEventPoint on-the-fly, containing only an id.
(That was unintentional, but perhaps useful sometimes.)
setExclusiveGrabber() looks up the persistent point, but if we emit the
signal with the given point, it is missing the device. A handler
connected to that signal might reasonably assume that the point is a
complete instance; so we'd better emit the complete instance that we
found. (OTOH if the given point was a detached instance, it might also
be unexpected that the signal emits the persistent instance instead of
the given instance.) Amends 2692237bb1b0c0f50b7cc5d920eb8ab065063d47
Change-Id: Iee16363dcb22c1dc07b0cc0a81930218e22fa19e
Reviewed-by: Volker Hilsheimer <volker.hilsheimer@qt.io>
Diffstat (limited to 'tests/auto')
0 files changed, 0 insertions, 0 deletions