The home button in every activity in my configuration jumps "Home" without terminating the activity. In order to go back to the current activity, the same button in the "Home" activity has a different action assigned to it - browse backwards. This way I can easily jump back and forth between the current and the "Home" activity using the home hard button only.

However, the problem now is that when I terminate the activity by pressing the power button, I no longer want the home button to take me back to the activity that is gone.

I know that I can duplicate the "Home" page/activity with different home button action, but I really want to avoid any duplication.

Note, this is TSU9300, so PS is not available.

Thanks!

Without ProntoScript your only option would be as you've stated, to duplicate your "Home" activity/page, so that the Home hard button could be set to something other than Browse Backward in that other activity/page.

As for the Browse Backward special action, it would be awesome to be able to clear the browse backward stack at will. I could see this being implemented as a new special action item (for editors which don't support ProntoScript) and/or via ProntoScript. I would find a feature like this very useful. Along these same lines, I've always wanted the ability to simply tag a given page, so that it was ignored by the browse backward stack which currently stores the last 9 page navigations. This would allow for the Browse Backward special action to be used in a more targeted fashion which is dynamic in nature over the use of a page jump. I submitted this idea as a feature enhancement on several occassions over the years going back to the early ProntoNG days. Would have been great to see it implemented. A classic example of where this could be used is with loading pages displayed during an activity macro where the main page of the activity you are taken to at the end of the macro includes a button assigned to Browse Backward. Being able to tag each loading page to be ignored by the browse backward stack would prevent the user from being able to browse back to the last of the loading pages from the main page of the activity for instance. They would instead be taken all the way back to the page they had come from prior to the first of the loading pages being displayed. Another good example would be pages under a given activity that you can cycle through via the Page Up/Down special actions. These types of pages you'd want to tag to be ignored by the browse backward stack as well as it would make no sense for you to want to browse back through them. If they were ignored by the browse backward stack browsing backward would simply take you back a step within the structure of your interface, a far more intelligent use of Browse Backward.