Мобильная версияНесколько экземпляров CLLocationManager, работающих параллельно ⇐ IOS
-
Anonymous
Несколько экземпляров CLLocationManager, работающих параллельно
There are some similar topics out-there, but mine is more specific, please bare with me (:
I have a single CLLocationManager that runs constantly while the app is open. it is very "lazy" CLLocationManager - has very low power consumption. both its desiredAccuracy and distanceFilter are very compromised.
on the other hand, I have another CLLocationManager that is quite the opposite. it has very good desiredAccuracy, and very short distanceFilter. but it only runs on specific scenarios (not constantly)
My question is:
can I be sure that both distanceFilter and desiredAccuracy will stay isolated for each CLLocationManager?
Can the accuracy for the 'lazy' LocationManager change due to running in parallel with the other one?
if not, are they any other configuration properties that might overlap?
Источник: https://stackoverflow.com/questions/780 ... n-parallel
There are some similar topics out-there, but mine is more specific, please bare with me (:
I have a single CLLocationManager that runs constantly while the app is open. it is very "lazy" CLLocationManager - has very low power consumption. both its desiredAccuracy and distanceFilter are very compromised.
on the other hand, I have another CLLocationManager that is quite the opposite. it has very good desiredAccuracy, and very short distanceFilter. but it only runs on specific scenarios (not constantly)
My question is:
can I be sure that both distanceFilter and desiredAccuracy will stay isolated for each CLLocationManager?
Can the accuracy for the 'lazy' LocationManager change due to running in parallel with the other one?
if not, are they any other configuration properties that might overlap?
Источник: https://stackoverflow.com/questions/780 ... n-parallel
