Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

binjaja

macrumors newbie
Original poster
Nov 13, 2008
10
0
The documentation says that after you specify startUpdating the delegate method locationManager:didUpdateToLocation:fromLocation will be called with a position that might not be within the desiredAccuracy. It could then be called again when the locationManager gets a better position. My questions:

1. Will the locationManager keep trying until it gets a fix within the desiredAccuracy and then call didUpdateToLocation
2. are there times when the locationManager gives up and CAN"T get a fix within the desiredAccuracy and therefore never calls didUpdateToLocation again? if so how does the application know if it gave up and whether to keep waiting or proceed with the less than accurate position?
3. Once the locationManager gets a fix within the desiredAccuracy will it try to get an even MORE accurate fix and call didUpdateToLocation again?


BTW.I read in another question on this post that CCLocationManager will always initially return the previous position in didUpdateToLocation and that you should wait for the second or third...is that true?? and if so, thats leads me back to my question above...how do you know when to stop waiting if the position never gets within desiredAccuracy?

Thank you!!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.