jgostylo wrote: > Thank you for the reply. You say to use unique LocationListener > objects. Is this because a single LocationListener is not set up to > handle multiple requestLocationUpdates or is there some other gotcha > that you are steering me from?
removeLocationUpdates() takes a LocationListener as its sole parameter. That is because the implementation of LocationManager holds onto a HashMap of listener info, keyed by LocationListener. Hence, if you try registering several with the same LocationListener, you are likely to run into problems. At best, last one in wins. At worst, last one in wins and you can never remove the first ones. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android Training in NYC: 30 April-2 May 2010: http://guruloft.com -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
