thats how android works. Please read android activity lifecycle. you can save state before the activity is destroyed and restore it after it is created.
-g On Apr 4, 10:50 pm, Gaurav Vaish <[email protected]> wrote: > Hi, > > I am working on a MVC implementation for Android (to be subsequently > hosted on SF and/or GC). > > It works like this: > > Activity (View) <=> Application (Controller) <=> Data (Model) <=> > Persistence (DB/Network etc) > > The scenario is: > > 1. Activity launch (main/launcher) > 2. Notifies Application about performing a data transaction > 3. Upon receipt of data response, controller devices which Activity to > launch (or update existing) > 4. Application has overridden the method onConfigurationChange > > Problem: > When the orientation is changed, the Application is notified about > onConfigurationChange but: > > a) The "current" activity is Destroyed and recreated -- which is fine > to some extent > b) The new instance which is created is automatically => onCreate, > onPause, onStop, onDestroy.... now that's catastrophic. > > Any guesses as to why the new activity is "killed"? :( > > Thanks in advance. > > Happy Hacking, > Gaurav Vaish -- 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 To unsubscribe, reply using "remove me" as the subject.
