Hi Alberto and all, I can see your point with setLastKnownPosition() but I agree that it could turn into 'asking for trouble' -feature.
I agree any assisted GPS should be fairly opaque to qt location API user. With 'fairly' instead of 'completely' I'm referring to QGeoPositionInfoSource::(set)PreferredPositioningMethods. Its backend dependant if AllPositioningMethods results to AGPS usage. Cheers, juha -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of ext Kevron Rees Sent: Thursday, September 30, 2010 5:27 AM To: Alberto Mardegan Cc: [email protected] Subject: Re: [MeeGo-dev] QtLocation MeeGo repository > void > QGeoPositionInfoSource::setLastKnownPosition(const QGeoCoordinate &); > > method, to initialise the positioning source to a known location. This > might help the engine to get the correct location faster. The use-case > of this is: last time I had my GPS on, I was in Helsinki. If now I'm in > Dublin and switch my GPS on, I could use some map application or widget > to pick Dublin as my known location, to get the fix faster. > > Does it make sense to you? > AGPS methods should be opaque to the application developer. It should all be done in the backend that talks to the hardware. cheers -000 _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
