Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
6.2.5, 6.3.1, 6.4.0 Beta3
-
None
-
-
5
-
c15525883 (6.4), 1fa695d4e (dev), 57794062a (tqtc/lts-6.2)
-
Foundation Sprint 72
Description
After QTBUG-103478 was fixed, we no longer explicitly request the location permissions when PositionSource is created.
Instead, we do it only when we start requesting position updates. That makes sense in general.
However, GeoFlickr example uses a bit different logic. It checks supportedPositioningMethods before starting updates. And if there are no available positioning methods, it tries to switch to simulation mode (which is currently broken because of QTBUG-105551).
After QTBUG-103478 is fixed, supportedPositioningMethods() always return nothing for a newly-constructed PositionSource, even if Location is enabled on Android.
Adding an implicit permissions request to supportedPositioningMethods() call does not look like a correct approach, because that would be basically similar to what we have fixed in QTBUG-103478.
So we need to find a way to rewrite GeoFlickr example...
Attachments
Issue Links
- relates to
-
QTBUG-105551 Missing nmeaSource property in geoflickr example
-
- Closed
-
- resulted from
-
QTBUG-103478 QGeoPositionInfoSource on Android always asks for location permission
-
- Closed
-
For Gerrit Dashboard: QTBUG-105558 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
437590,14 | Refactor geoflickr example | dev | qt/qtpositioning | Status: MERGED | +2 | 0 |
448070,2 | Refactor geoflickr example | 6.4 | qt/qtpositioning | Status: MERGED | +2 | 0 |
448101,3 | Refactor geoflickr example | tqtc/lts-6.2 | qt/tqtc-qtpositioning | Status: MERGED | +2 | 0 |