If you look in DDMS, the resources are kept in memory even after
onDestroy has been called. This is, as far as I can tell, for faster
startup times.
I too would like further information on this. So far I haven't gotten
any good answers. I am hoping that we will not have to explicitly
initialize every static value in onCreate, given the probability of
bugs in overlooking even one thing.
On Apr 22, 5:11 am, vitvikt <[EMAIL PROTECTED]> wrote:
> Hi,All
> Can anybody answer, why static variables save its values between
> onDestroy() in first
> application's call and onCreate in second application's call?
> In documentation I read:
>
> "The entire lifetime of an activity happens between the first call to
> onCreate(Bundle) through to a single final call to onDestroy(). An
> activity will do all setup of "global" state in onCreate(), and
> release all remaining resources in onDestroy(). "
>
> But in example I see, that TestValue savd it's value between calls
> public void onCreate(Bundle icicle) {
> super.onCreate(icicle);
> if(TestValue==0)
> TestValue=1;
>
> Thank's
> vitvikt
--~--~---------~--~----~------------~-------~--~----~
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]
Announcing the new M5 SDK!
http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html
For more options, visit this group at
http://groups.google.com/group/android-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
