On Sat, Aug 14, 2010 at 7:04 PM, viktor <victor.scherb...@gmail.com> wrote: > Thanks Sebastián, > > But render different views on the same activity it is not good, it is > better for desktop app but not mobile. Because Android cashed activity > to prevent rendering the same type views.
Thats not a fact. It depends on how you really are creating an Activity, or you just simply are displaying more information about the same thing you showed before (thats why the _recomendation_). An Activity should be a task. > It is need investigate your thing that activity which in background > can be killed. Activity1---Activity2--Activity3. I think that > Activity1 never will be killed. Well, the activity life-cycle does not say that: http://d.android.com/images/activity_lifecycle.png Check the flow to "process is killed" when memory is needed. Every time activity is paused/stopped, your Activity may be destroyed. > If we have low memory, another application process will be killed but > not active application. And AFAIK, destroying an Activity does not means killing your whole Application. Regards, -- If you want freedom, compile the source. Sebastián Treu http://labombiya.com.ar -- 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 android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
