Have Activity B call Activity C using startActivityOnResult(intent, requestCode), override Activity C's onBackPressed to pass a kill flag via intent and setResult. In Activity B override onActivityResult and see if the kill flag is there and the request code matches then call finish(). So pressing back in C will go to A.
On May 30, 3:22 pm, Fina Perez <[email protected]> wrote: > Hi! > I thought to use that, but I'm not sure if it's going to work. The > thing is sometimes I break the "normal flow" between activities, I > mean, from activity A I start activity B, and from B, C. But when I > finish activity C, I go back to the activity A, so I really dont know > if onStartActivityForResult waits for the result of the activity it > launched or just for a result. > > On May 26, 7:56 pm, TreKing <[email protected]> wrote: > > > > > > > > > On Thu, May 26, 2011 at 3:44 AM, Fina Perez <[email protected]> wrote: > > > when I press the back button and navigate from one activity to the > > > previous > > > one inside my app. In this case, I dont need to check anything, but I > > > really > > > dont know who to handle this situation. > > > > any ideas? > > >http://developer.android.com/reference/android/app/Activity.html#star..., > > int)http://developer.android.com/reference/android/app/Activity.html#onAc..., > > int, android.content.Intent) > > > --------------------------------------------------------------------------- > > ---------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices -- 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
