1

I'm wondering why making activity singleTask destroys the stack after returning to it. For example, with standard type if we adhere to rules, another instance of first activity should start again, but it doesn't. What's so special in singleTask? P.S. I saw this discussion: Android: bug in launchMode="singleTask"? -> activity stack not preserved

Community
  • 1
  • 1
Konstantin Milyutin
  • 11,946
  • 11
  • 59
  • 85

1 Answers1

2

Check out the answer at Android singleTask or singleInstance launch mode? - which does a good job if explaining the documentation and refers on to an excellent blog / android app (at http://blog.akquinet.de/2010/02/17/android-activites-and-tasks-series-an-introduction-to-androids-ui-component-model/).

Community
  • 1
  • 1
Torid
  • 4,176
  • 1
  • 28
  • 29
  • Just started reading those blog posts; they're a very good, clear explanation of what's going on with Intent flags and Activities. Far better than the manual! – Matt Gibson Apr 25 '12 at 07:22