UBZack wrote: > I did a little poking around and I think I can DEFINITELY shine some > light on this. > > Basically, I think the difference lies in the way Eclipse ports the > apk to the emulator and launches it.
<lengthy detailed analysis snipped> > It seems that eclipse ports the app to the emulator in such a way that > each successive launch that is made while the app is running pushes > another instance of the app onto the stack, unless you hit the back > button before relaunching. I don't use Eclipse. If I understand correctly, from this post and others, is that when you run the application from Eclipse, you are taken right to the initial activity of that application, bypassing the home screen and launcher. In that case, what may be happening is that Eclipse tells the emulator to launch the root activity...and specifies FLAG_ACTIVITY_NEW_TASK and FLAG_ACTIVITY_MULTIPLE_TASK on the launching Intent. That would provide the behavior you're experiencing, if I understand correctly. > Any light that you guys can shine on this would help a lot, and well > done on providing very helpful examples and suggestions Clearly, Eclipse is part of a broader Hulu-led initiative to "turn our chunky brain matter into creamy goo". ;-) > Mark, you've been quite a legend on this forum! Legend? I hope not. Legends are frequently rather dead. But, thanks! -- Mark Murphy (a Commons Guy) http://commonsware.com | http://twitter.com/commonsguy Android App Developer Training: http://commonsware.com/training.html --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
