You could override onResume as well, have it check a flag set in onCreate to distinguish between the first original callback sequence and subsequent ones, and clear some data values. 20.04.2011 11:03 пользователь "String" <[email protected]> написал: > I've been bothered by this issue myself for a while. Streets' solution works > in the scenario where the system kills the activity in the background, but
> not when the user exits the activity with the Back button, then later > returns to it by a long-press of Home: the "Recents" list re-launches the > app with the last-used Intent, and savedInstanceState isn't preserved. If > the Intent in question was meant to be a one-shot (it has Extras which have > been "used up"), then you're back in the same, unwanted situation. > > Any thoughts? I could certainly save something to SharedPrefs which would > work around this, but it seems like overkill. > > String > > -- > 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 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
