On Thu, Aug 4, 2011 at 9:31 AM, Chris J. Karr <cjk...@gmail.com> wrote: > The simplest solution would be to ignore Geocoder altogether (and just > use a custom lookup method), but in the spirit of doing things the > "Android way", I was wondering if it was possible to override the > system provider Context.LOCATION_SERVICE with one of my own and have > Geocoder use my implementation (just for my own app).
You are welcome to extend Activity and override getSystemService() to do whatever you want. Geocoder won't use it, because it does not use a LocationManager directly. I'm also unclear why you think this is "the Android way". If you want to roll your own geocoding logic, ignore Geocoder and LocationManager and just roll your own geocoding logic. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in NYC: http://marakana.com/training/android/ -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
