Ok, finally had time to play with this...and it is great. Thanks for getting this feature in!
support wrote: The next beta of Indigo Touch will have something in place to try, although I'm not sure if it is the long term solution we want. Stay tuned...
It's not the long-term solution I'd like
. I'm trying to get rid of the bottom navigation bar. I have one top-level control page that acts as a main menu to go into sub pages (e.g. iTunes, Sprinkler system, Lights). For each icon in my main menu, I have it set to a client action to load an external URL, such as "indigo://controlpage/Lights?action=showPage". This works great to remove the bottom nav bar from all subsequent pages. However, there are three problems: 1) it only works for Indigo Touch (and not in Safari -- Safari won't load the page at all, of course); 2) if you quit Indigo Touch and then start it again, it defaults to showing the bottom nav bar, and; 3) the use of this external URL causes the "back" button on the top nav bar not to show (which makes sense if was truly an external URL).
Although I seem to use Indigo Touch more often than not, I hate to do things that'll cause me to code twice - once for Indigo Touch, and once for the web browsers.
As dnomode requested:
dnomode wrote:Please give us on/off setting for these view options
I'd also like to see an on/off toggle as a property of each control page, although if it was a global option in Indigo Touch, I'd be a happy camper. Whatever the solution, please keep the options for disabling the top and bottom nav bars separate. Despite my previous comments about the top nav bar taking up too much real estate, I've decided that I actually like it because of its back button. Now I'm only on a crusade against the bottom nav bar
.
Another modification you might consider to control pages is to have both a "Page Name" for Indio.App usage and add a "Display Name" that is actually displayed in the top nav bar. This could help with the fact that Indigo allows the use of characters in control page names that aren't valid in URLs (such as "/") which poses a problem when you try to access it that way.
Rick