CLLocationManager Singleton - is this the way to go?

I'm building an app with two simple views (in a tabbar).

  • first view: it should show the user's location (default blue dot) and load data from a server.
  • second view: it should show the user's location (my custom pin with annotation and callout). the user can tap the callout and submit data about the current location.

I started by using MKMapView's showsUserLocation. Then I read that it's better to use a CLLocationManager singleton instance, so I followed this blog post roughly:

Now this pretty much works, but I'm wondering if it's the correct way to do things.

Also, I couldn't find a way to show the default blue dot instead of a custom pin. I read that I should use MKMapView's showsUserLocation, but wouldn't that create another instance of CLLocationManager?


-------------Problems Reply------------

The method of creating a CLLocationManager singleton in the blog post you mentioned looks good. As for using showsUserLocation in combination with a CLLocationManager, it should be fine. Apple designed Core Location to be used by multiple applications at once. I won't cause too many issues.

Category:ios Views:0 Time:2011-05-14

Related post

Copyright (C), All Rights Reserved.

processed in 0.099 (s). 11 q(s)