If you press back and arrive at the same activity you started on, I think that's a bug that I've only seen when using Eclipse to develop. I think if you press back as far as you can possibly go, until you reach the home screen, then run the app from the phone (not from eclipse) it will behave normally. Running the app from the IDE seems to screw around with the task stack for some reason.
On May 9, 3:49 pm, Mariano Kamp <mariano.k...@gmail.com> wrote: > I still don't get it ;-( > I have the top level activity, let's call it A, that is used by the launcher > and have the android:clearTaskOnLaunch attribute set to true. A drills down > to B and B to C. > Now when I am on activity C and switch to Gmail and back to my app/task then > C is up. > If I launch the task activity A is displayed not C, which is what I want. > But when pressing Back on A I get to A again. That doesn't seem right to me. > Shouldn't A have been cleared too, so that Back would return me to the > launch screen? > > On Fri, May 8, 2009 at 5:08 PM, Mariano Kamp <mariano.k...@gmail.com> wrote: > > Isn't that the same model that is used on the Desktop?Launching an app > > usually puts you in a clean state, but switching back to a running instance > > (Alt/Cmd+Tab) brings you to the screen of the app you were most recently > > on.That makes perfect sense to me. > > > Actually now that I learned about android:clearTaskOnLaunch [use in > > contacts<http://android.git.kernel.org/?p=platform/packages/apps/Contacts.git;...>] > > here, I can finally try to get my app to behave like I would expect it to. > > > This discussion is very enlightening. Dianne that would be a great topic > > for a blog post of yours, wouldn't it? ;-) > > > On Fri, May 8, 2009 at 3:07 PM, Mike Hearn <mh.in.engl...@gmail.com>wrote: > > >> > As far as contacts goes, though, this is actually intentional -- some > >> apps > >> > (like contacts and settings) want to put the user back to their front > >> door > >> > when relaunched from home, so they set the option to do that. This is > >> > actually a "desired" inconsistency. > > >> Right, I realise it's intentional. What I'm unclear on is, why these > >> apps are special? I presume usability testing revealed this is the > >> behavior users expected. In which case why not reset task stacks for > >> every app? > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
