As internally accuracy just sets<http://androidxref.com/4.4_r1/xref/frameworks/base/location/java/android/location/Criteria.java>`mHorizontalAccuracy` I wonder why both setHorizontalAccuracy() and setAccuracy() - and no less than 6 constants - are provided.
Anyone knows ? On Tuesday, November 5, 2013 12:48:54 PM UTC+2, Mr&Mrs D wrote: > > setAccuracy<http://developer.android.com/reference/android/location/Criteria.html#setAccuracy%28int%29> > > > Indicates the desired accuracy for latitude and longitude. Accuracy may > be ACCURACY_FINE if desired location is fine, else it can be > ACCURACY_COARSE. More accurate location may consume more power and may take > longer. > > setHorizontalAccuracy<http://developer.android.com/reference/android/location/Criteria.html#setHorizontalAccuracy%28int%29> > > > Indicates the desired horizontal accuracy (latitude and longitude). > Accuracy may be ACCURACY_LOW, ACCURACY_MEDIUM, ACCURACY_HIGH or > NO_REQUIREMENT. More accurate location may consume more power and may take > longer. > > Another example of the pristine android docs. So what is the difference ? > Notice they take different constants - is it possible/desirable to specify > both with some combination of constants ? > > asked also > here<http://stackoverflow.com/questions/17599719/setaccuracy-vs-sethorizontalaccuracy> > > -- 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 --- You received this message because you are subscribed to the Google Groups "Android Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
