diff options
| author | Michal Klocek <michal.klocek@theqtcompany.com> | 2015-07-09 08:28:42 +0200 |
|---|---|---|
| committer | Michal Klocek <michal.klocek@theqtcompany.com> | 2015-07-13 14:31:23 +0000 |
| commit | c93d0f85b2b1fbd623a938c0d1a0d7c6ea0d784f (patch) | |
| tree | 8ff6163c850db156c84658ff5086b9b3bba79614 /examples/location | |
| parent | 0891ea11e0000289354ab62f8c4c3d21e008823a (diff) | |
| download | qtlocation-c93d0f85b2b1fbd623a938c0d1a0d7c6ea0d784f.tar.gz | |
Do not rely on synthesized MouseReleseEvent when tracking mouse point
A map pan is based on synthesized events due to the fact that
rest of qt (qtcontrols , mouse area etc) depend on it in case of touch
handling. However when there are two touch points on the screen
pinch handling is activated. After accepting the touch event,
mouse synthesized events are no longer generated for the first touch
point, what's more as a result we might not get even
mouseUngrabEvent nor mouseReleaseEvent. This breaks internal
tracking of mouse position. This workaround resets mouse tracking point
in case of getting touchUngrabEvent.
Remove dummy extra MouseArea from places example.
TODO: fix broken mouse area state in pinch unit tests
Task-number: QTBUG-46388
Change-Id: I5588fbd4dbf0c5d25c44f994292c1aae7b3d70d4
Reviewed-by: Alex Blasche <alexander.blasche@theqtcompany.com>
Diffstat (limited to 'examples/location')
| -rw-r--r-- | examples/location/places/items/MapComponent.qml | 5 |
1 files changed, 0 insertions, 5 deletions
diff --git a/examples/location/places/items/MapComponent.qml b/examples/location/places/items/MapComponent.qml index ccf1415d..de4e04a7 100644 --- a/examples/location/places/items/MapComponent.qml +++ b/examples/location/places/items/MapComponent.qml @@ -211,9 +211,4 @@ Map { map.zoomLevel = value } } - - MouseArea { - //workaround for QTBUG-46388 - anchors.fill: parent - } } |