> > That process requires the exact same onCreate()/onResume(), you just > don't realize it because it happens transparently for Views: >
My testing shows starting an external activity and then returning via the back key only calls onResume, not onCreate. The screen orientation change calls both onCreate and onResume on the originating activity. It seems odd (maybe a design flaw, grin) that starting another activity which in essence leaves my app causes less disruption to the original activity than a process that rotates the screen while I am STILL in my app. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
