OK. I may have have to throw my computer out a very tall window! With Dianne's hints here and there, I'm able to surmise what might be happening. When I initially launch the app, I do it from an IDE. The IDE uses the following command to start the app:
am start -D -n "com.mycompany/A1" The generated intent is: flg=0x10000000 cmp=com.example/.MyActivityA1 This is necessarily not the same as the HOME/LAUNCHER, where the generated Intent is: act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.example/.MyActivityA1 Diane indicates your Intents have to match when launching a new Task, or you get a different task at runtime. What is really confusing, however, is that even though the initial launch (by the IDE), and the subsequent re-launch after HOME by the LAUNCHER are using different Intents, the Task stack I posted above shows the two "copes" of A1 in the SAME Task record. It's just that instead of resuming the Task where it left off, it resumed it and THEN added a duplicate of A1 on the top of the stack. Can you explain why this level of detail occurred Dianne? -- 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
