It means the system can free up memory from the pieces of your application that aren't in use.
Secondly, it means your application is monolithic, preventing other applications from interacting well with your application. If an application is broken into multiple activities, another app (or user, with the help of things like Any Cut) can "bookmark" a page inside your app, invoking the relevant data. Anm On Oct 24, 10:55 am, "Robert K." <[EMAIL PROTECTED]> wrote: > oops, not setContentPane put setContentView :-) > > On 24 Okt., 19:54, "Robert K." <[EMAIL PROTECTED]> wrote: > > > Question: Why is it better to start a new activity if you want to > > change screen to a new view (for example to edit some notes on a > > separate text field)? > > > You could get the same result by taking setContentView(newView) which > > offers several advantages as far as I can see. Are there any > > consequences, if I pack every single view of my application into one > > single activity? Or are both ways equivalent? If yes, I would prefer > > setContentView(...) for many reasons. > > > Thanks in advance for your answers. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
