packageandroid.app goes through the entire application load & remover giving several places to put code ~ you just implement the methods - how a:b:c call chain would be manages is startActivityForResult
copy-paste from the search result for that term is Activity | Android Developers To do this, you call the startActivityForResult(Intent, int) version with a second integer parameter identifying the call. The result will come back through your ... developer.android.com/reference/android/app/Activity.html On Nov 2, 2:02 am, Assaf <[email protected]> wrote: > Update - Answer to 2 is Yes. > > On Oct 27, 6:48 pm, Assaf <[email protected]> wrote: > > > > > > > > > As I now understand, Android will start the top-most activity even > > after killing the process due to resource shortage. > > (seehttp://groups.google.com/group/android-developers/browse_thread/threa... > > ) > > > My root activity is responsible for some initialization code that I > > wouldn't like to bother-with from other activities. > > > Questions: > > > 1. Any way to change this behavior and ask Android to clear the task > > when killing my process ? > > > 2. If not, what will happen if the user press BACK in such scenario ? > > will Android re-create the next activity in the stack ? i.e. stack > > has activities A,B,C. process is killed. User re-selects my app, > > Android creates *C*, user presses BACK. will Android now create B ? > > > Thanks. -- 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
