On Sun, Sep 26, 2010 at 12:06 PM, Lucas Boucher <[email protected]> wrote: > I don't see how my calls to onStart() > would cause this specific issue and don't want to fix something that isn't > broke just to make code look better.
Except it is broke. Do not call onStart() of an activity yourself, please. > All my app needs to do is go thru a sequence of checks, gps, gps init, > internet availability, is my location in some list, then display a pic. > If it fails anywhere along the line I wanted to throw a dialog box. > The user can check whatever errored. > Then i just want to run thru the whole sequence again. Then move "the whole sequence" into another method, that you call from onStart() and your dialog button. > Thus I called onStart(). This does not "start the whole program again". What it will do is confuse the heck out of the Activity base class. Do not do this. While restarting your activity seems like a wasteful solution, to do this, call startActivity(getIntent()), followed by finish(). The first statement should run another copy of your Activity; the second statement will get rid of your existing copy. -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training...At Your Office: http://commonsware.com/training -- 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
