To Boston, we should suggest to android developers to use fragments and onSavedInstanceState...
On May 16, 4:43 pm, sblantipodi <[email protected]> wrote: > Open the browser, fill in some blank spaces, now multitask, reopen the > browser, the page is completely reloaded, > do you think that the developers who wrote the android browser don't > know how to implement an activity? :D > > On May 16, 4:16 pm, Nikolay Elenkov <[email protected]> wrote: > > > > > > > > > On Wed, May 16, 2012 at 11:01 PM, sblantipodi > > > <[email protected]> wrote: > > > As the graph I posted explain the app is not restarted, but the latest > > > activity is. > > > If the activity is restarted, user needs to reinput the input it > > > submitted, variables needs to be re-populated, etc. > > > Well, Android does this for you *if* you implement your > > activity properly. You should read how the activity lifecycle > > works, not just look at the graph. > > > > from your talking it seems that in your mind the app needs to store > > > every user's move in database > > > and restore it in every onCreate(), hey, have you every programmed an > > > android app? > > > See above. > > > So what is your definition of a 'non-broken multitasking system' again? -- 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
