Tuesday, March 20, 2012

Re: [android-developers] LocationManager requestLocationUpdates minTime parameter not working

On Mon, Mar 19, 2012 at 8:28 PM, StarTraX <gpsanimator@gmail.com> wrote:
> I'm really fed up reading about the min time and min distance being "a
> hint".

Minimum time is a hint. Minimum distance is honored as a filter.

If there's a complex interaction between our parameters and the
> resulting effect, why isn't it documented?

Because LocationManager supports an arbitrary number of location
technologies, and those location technologies may use the minimum time
in different ways. This is a common approach with abstraction
patterns, as experienced developers should recognize.

> Just how the heck does it work?

You are welcome to read the source code to examine the current
behavior. Just bear in mind that this behavior may be different than
with past versions, may be different in future versions, may be
different with manufacturer-specific location technologies, etc.

--
Mark Murphy (a Commons Guy)
http://commonsware.com | http://github.com/commonsguy
http://commonsware.com/blog | http://twitter.com/commonsguy

Warescription: Three Android Books, Plus Updates, One Low Price!

--
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en

No comments:

Post a Comment