At 7:19 AM -0700 4/24/09, chrispix wrote:
>
>Having to prompt the user each time to turn on / off gps is a giant
>pain from the standpoint of program flow.
I'm not sure why you have to prompt each time. You only need to check
the GPS state once at startup and then fire the user off to settings
if it is not on. They press "back" after that and you're on your way.
> Can't there be some way to code GPS state to an application state?
I'm having a hard time understanding most of your writing, but do you
mean doing something like this:
public static boolean gpsEnabledInSettings( final Context context )
{
android.location.LocationManager alm =
(android.location.LocationManager)
context.getSystemService( Context.LOCATION_SERVICE );
return alm.isProviderEnabled(
android.location.LocationManager.GPS_PROVIDER );
}
...or are you proposing a manifest entry staying your app only wants
to run with GPS on? or?
Sure it is nice to be able to provide an "in application control" but
it is not strictly a requirement for operation. This just does not
seem to me to be that big a deal. Am I missing something?
-- Ward
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
