It turns out that "singleTask" is what I need in my app for my main (LAUNCHER) activity otherwise sometimes I end up with multiple instances of my activities.
On Aug 22, 10:33 am, Gil <[EMAIL PROTECTED]> wrote: > If I use "singleTop" for both activities the code works as expected. > The "singleTask" launchMode is causing the behavior described > above. --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new Android 0.9 SDK beta! http://android-developers.blogspot.com/2008/08/announcing-beta-release-of-android-sdk.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
