diff options
| author | Bradley T. Hughes <bradley.hughes@nokia.com> | 2010-02-12 15:18:07 (GMT) |
|---|---|---|
| committer | Bradley T. Hughes <bradley.hughes@nokia.com> | 2010-02-16 09:54:04 (GMT) |
| commit | f3a47f0fe6e9f63c030e6e89f1258d4faf2025cd (patch) | |
| tree | 4e0316577caa4e7d91d4c9048fe3773d6751ecfb /src/corelib | |
| parent | 435fa2dbc44868f6ac81956be82631a2040ed1cc (diff) | |
| download | Qt-f3a47f0fe6e9f63c030e6e89f1258d4faf2025cd.zip Qt-f3a47f0fe6e9f63c030e6e89f1258d4faf2025cd.tar.gz Qt-f3a47f0fe6e9f63c030e6e89f1258d4faf2025cd.tar.bz2 | |
Don't crash when QTouchEvent is accepted but not handled by a
QGraphicsItem
After propagating QEvent::TouchBegin, if there is no item that has
accepted and handled the event, we must remove the touch point from our
data structures.
In this situation, QGraphicsScene will ignore the TouchBegin, as will
QGraphicsView, and QApplication will respond by not sending any more
touch events to the view/scene/item. This means our logic for handling
TouchPointReleased points will never be called (and the QGraphicsScene's
itemForTouchPointId and sceneCurrentTouchPoints state will be
incorrect).
Reviewed-by: Denis Dzyubenko
Reviewed-by: Marius Storm-Olsen
Diffstat (limited to 'src/corelib')
0 files changed, 0 insertions, 0 deletions