diff options
| author | Shawn Rutledge <shawn.rutledge@digia.com> | 2014-04-04 09:44:07 +0200 |
|---|---|---|
| committer | The Qt Project <gerrit-noreply@qt-project.org> | 2014-04-04 10:46:21 +0200 |
| commit | ba2ea6da298bfd234af1afeaf154fa4aaefaad88 (patch) | |
| tree | 083ccb2350a907e7669d137f0052bab8fb5c47f2 /mkspecs/qnx-armle-v7-qcc/qmake.conf | |
| parent | 11b8794456e4abb5c2068bb1ee1067fcdf79baa1 (diff) | |
Don't assume qt_tablet_target widget exists from one event to the next
In this scenario there is a widget with a button inside, and you click
the button with the tablet. The target of the event is the button,
but when you click it, the parent (or ancestor) is destroyed. Commit
2bac49265efcf8faabc3756d1a3e405a3d336f68 took care of the case when
the parent is a window, but it is not always a window which is being
destroyed. So the approach of using a QPointer is better because it
should take care of all the cases when the qt_tablet_target is
destroyed during the course of a tablet event sequence.
Task-number: QTBUG-36848
Task-number: QTBUG-38040
Change-Id: Ia0e861f2cb2fbc30234aa596f3a36ddd0835a9af
Reviewed-by: Laszlo Agocs <laszlo.agocs@digia.com>
Diffstat (limited to 'mkspecs/qnx-armle-v7-qcc/qmake.conf')
0 files changed, 0 insertions, 0 deletions