summaryrefslogtreecommitdiff
path: root/src/plugins/geoservices/osm/qgeotileproviderosm.cpp
diff options
context:
space:
mode:
authorFrederik Gladhorn <frederik.gladhorn@qt.io>2016-09-29 23:23:25 +0200
committerShawn Rutledge <shawn.rutledge@qt.io>2016-10-04 12:24:17 +0000
commita65d9b7acf62fdafd670b40c01425cedff61106c (patch)
treeac1216905091a046daab265a536063217335ec29 /src/plugins/geoservices/osm/qgeotileproviderosm.cpp
parent4be48cf9ee320f779e3e37db34865faac86fcc17 (diff)
downloadqtlocation-a65d9b7acf62fdafd670b40c01425cedff61106c.tar.gz
Remove a bunch of ungrabTouch/Mouse calls
Ungrabbing means actively not wanting to receive any future events. With slight changes in the event delivery in Qt 5.8, this leads to release events not being delivered to the items, which in turn means that the map thinks it's pressed after the last touch is gone. There is no reason to call ungrab at all, when an event ends in a regular way (release/cancel). The only reason to ungrab is when for some reason future move/release events are unwanted, in which case the item needs to make sure it's in the right state (as in not expecting release events to follow). Task-number: QTBUG-56213 Change-Id: Ieb8dbf4d8ab312cff461c4fe8a3621af67a132b9 Reviewed-by: Paolo Angelelli <paolo.angelelli@theqtcompany.com> Reviewed-by: Shawn Rutledge <shawn.rutledge@qt.io>
Diffstat (limited to 'src/plugins/geoservices/osm/qgeotileproviderosm.cpp')
0 files changed, 0 insertions, 0 deletions