Agreed, this still confuses me. If you browse the Android Developers group Hackbod has gone into some more detail on the subject. Frequently developers end up using SingleTop or SingleTask in a way that isn't recommended.
Perhaps some example use cases, and the recommended way to solve the problems that lead developers to the appmodel page. (Wanting to avoid multiple instances of activity being created). On Jan 14, 8:52 pm, jtaylor <[email protected]> wrote: > I think this page needs to be rewritten. I've been looking at it for > months and I still can't understand it. And I doubt many others do > either. > > Android Application Model: Applications, Tasks, Processes, and > Threadshttp://code.google.com/android/intro/appmodel.html > > For Instance: > "The singleInstance launch mode is even more specialized, and should > only be used in applications that are implemented entirely as one > activity." > > This sentence doesn't really give a definition of singleInstance. It > just says when it should be used. And that it's "specialized". > > - Juan T. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Beginners" 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-beginners?hl=en -~----------~----~----~----~------~----~------~--~---
