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.
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. If we have low memory, another application process will be killed but not active application. On 14 Сер, 23:47, viktor <[email protected]> wrote: > At the First that is rule from customers. (It is need improve why this > issue doesn't implemented or implement it) > At the second my method call many other processes, it call if main > activity is started and ..... (I want implement it when app is returns > to the foreground). If I call it when new activity or previous > appear, I thingApplicationwill be crashed. > > Is it possible to do that by getting current device activitystate? > (fore example PropertyActivity(cashed) ; MapActivity(cashed) ; > MyActivity(active)) > > On 14 Сер, 23:23, TreKing <[email protected]> wrote: > > > > > On Sat, Aug 14, 2010 at 3:04 PM, viktor <[email protected]> wrote: > > > I try call my method in all Activity life cycle methods but result > > > the same, my method calling always, when activity is coming to > > > the foreground, back to previous activity, start new activity. > > > WHY does it matter if you're returning from Home screen or another Activity? > > > --------------------------------------------------------------------------- > > ---------------------- > > TreKing <http://sites.google.com/site/rezmobileapps/treking> - Chicago > > transit tracking app for Android-powered devices -- 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
