my bad! I had a base class activity that all my activities were deriving from and in the base class i was not calling the super methods in key (pun intended) areas where I should have been. thanks everyone for your help. *sigh*
tia. On Sep 4, 9:29 am, sdphil <[email protected]> wrote: > i added: > > @Override > public void onPause() { > super.onPause(); > } > > @Override > public void onStop() { > super.onStop(); > } > > to the activity I'm going TO and set a breakpoint on each of the > super.* calls. > > I run the app again, started with an activity, then started the other > activity, hit the "back" button and neither breakpoint triggered... > > tia. > > On Sep 2, 1:11 am, Lee <[email protected]> wrote: > > > I also highly recommend logging in > > onpause,onstop,ondestroy,onresume,onstart,oncreate,onsaveinstancestate,onrestoreinstancestate,onuserleavehint > > so > > you can see what is happening when. > > > Lee > > > On Sep 2, 3:00 am, sdphil <[email protected]> wrote: > > > > I have a bunch of activities that are launching each other through > > > intents. somehow, i got into a code state where some of the screens > > > the back button (physical button) works, but others it does not. > > > > I didn't do anything intentionally to disable the back button - what > > > could be causing the back button not to work? > > > > tia. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
