What if you make your activity singleTop and then use onNewIntent() in the same
activity such as
onCreate { configure(); }
onNewIntent { configure() }
-----Original Message-----
From: Daniel <[email protected]>
To: Android Developers <[email protected]>
Date: Fri, 3 Jul 2009 00:38:44 -0700 (PDT)
Subject: [android-developers] Activity Lifecycle
>
> Hi,
>
> I did an activity that reads a lot of preferences stuff in its
> onCreate and configures the app accordingly. Since there is also some
> multithreading going on in this activity reconfigureing after some
> preferences change during runtime would be a complicated and error
> prone task. So I decided to simple launch a new instance of the
> activity after preferences changed and forget about the old one. I did
> this using:
>
> finish();
> startActivity(getIntent());
>
> But now I don't understand the activity lifecycle anymore. The
> onCreate, onStart and onResume callbacks of the new activity are now
> called before the onStop and onDestroy callbacks of the old activity I
> want to replace. Only onPause is called before the new activity
> starts.
>
> May this also happen when not exclicipely restarting the activity.
> Maybe when changeing the device's orientation?
>
> Or is the above finish, startActivity sequence simply not a good
> idea ;-). Is there no other way how an activity can restart itself?
>
> Best regards,
> Daniel
> >
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
