diff options
author | Shawn Rutledge <shawn.rutledge@qt.io> | 2017-02-14 10:04:49 +0100 |
---|---|---|
committer | Shawn Rutledge <shawn.rutledge@qt.io> | 2017-02-21 15:28:36 +0000 |
commit | 507efe5a8a2390813fb620a91b0b3b6b383f599d (patch) | |
tree | f60fdb68f5af695197673706fa5a6d3a0c93bfbe /tests/manual | |
parent | 8967a1b7b86306879a3113b290610b03727670ff (diff) |
unify handler grab state handling into onGrabChanged
onGrabChanged and handleGrab looked redundant. It was also not clear
how important it is for handlers to react to passive ungrabs, overrides
or cancellations. Rather than debating about when to call one of these
and when not to, let's centralize the responsibility in
QQuickEventPoint (because the grabber pointers are stored there, so
it's the ultimate destination of any grab change), and let's notify
all the relevant handlers about all changes, with enough information
that each handler can decide for itself what's important and what
isn't. But so far most handlers don't need to override this virtual.
The base class QQuickPointerHandler takes care of setting the
active property to false, rejecting the eventpoint, and unsetting
keepMouseGrab and keepTouchGrab whenever grab is lost; and emitting
grabChanged or canceled as appropriate to notify any QML code which
needs to know. Subclasses mainly care about the change of active state:
they must initiate active state themselves, and may react when it
reverts to false.
Change-Id: I6c7f29472d12564d74ae091b0c81fa08fe131ce7
Reviewed-by: Jan Arve Sæther <jan-arve.saether@qt.io>
Diffstat (limited to 'tests/manual')
0 files changed, 0 insertions, 0 deletions