I found the answer here how to kill sub activities and bring activity to top of stack.
I don't know if you actually can manipulate the stack of application like your suggesting in your title. My app runs in opengl so I never actually change form one Activity to another but I think the following principle will also work: Why don't you call the Activity you want yourself? It is really straight forwards in the back button event to handle this.
On back pressed -> load activity you want if your in activity A then exit.
I thought of that too but the code some how doesn't look clean to me. I just found another answer Thank you for your contribution. – Ragunath Jawahar Nov 22 '10 at 5:46 no problem, I'm just glad you found the answer you needed ^^ – Jason Rogers Nov 22 '10 at 5:48.
When the user navigates from A -> C he should be able to get back to the previous activities by pressing the back button. But after reaching D pressing the back button should take him to activity A. And pressing the back button againg should exit the application instead of taking him back to B / C / D.
How do I do it.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.