The JSON parameter to hide the tab bar is saving the incorrect parameter name. Existing control panel saves: "hideTabBarWhenScreenLoads" should be "hideBottomTabBarWhenScreenLoads" Every time I save something on that screen in the control panel, I need to re-change the parameter manually in the JSON again, which is a pain, lol. Please fix it so I don't have to feel such pain.... :)

I wonder if using the 'stobe snippet keeper' could bandaid the issue in the interim... :) Cheers! -- Smug

When ever I set that in the control panel I couldn't work out what the effect was supposed to be...

@AlanMac : That's because it's broken. You can manually change the JSON parameter at the bottom by adding "Bottom" in the middle of the word, but every time you click save on that screen, the control panel doesn't know where to save that parameter so it deletes it. @Smug : I could certainly take advantage of that AMAZING feature. But the snippet keeper is best utilized to rapidly and massively reproduce screens after they're all setup. It's the process of setting up the first menu screen that is what I'm battling with. The bottom line is: I know what I'm doing. I'm just trying to make it easier for those that might just be starting. Stobe

Hi Stobe, I understand the problem, I just don't know what the effect you are supposed to see if you have it working. To expand, is it only for tabbed apps? And does it hide the tab for second or so when a plugin is loading or transtioning from another menu?

Yes, it only applies for a tabbed app. And it's purpose is to hide the tab bar when the page loads (and stay hidden for the duration). This effect obviously doesn't work on screens that are on your tabs. (Can't hide the "home" screens of the 5 tabs you have). But and sub-screen from those tabs can hide the tab bar to allow you to utilize the whole screen. The only screen that hides the tab bar by default is the quiz screen. All others require the hideBottomTabBarWhenScreenLoads parameter. Hope that clarifies.

I don't use tabs in my apps much, so a bit hazy on some of the techniques. thanks for the explanation Stobe, appreciated.

This one piqued my interest. Thinking about it, I realise I've tried this feature before and not observed any effect, I think because the plugin I tried it on didn't support it. Looking at the code, it turns out there several plugins where this isn't supported. I looked at my menu plugins, they don't support this either - I'll fix that asap. Thanks for the heads up Stobe.

This issue has now been fixed. :)

Uh oh. I should have replied back here again. I think as it turns it, most of the plugins were using the 'wrong' parameter, and after looking further it was easier to just change it in the source code for iOS. I'm not sure what android uses though. I hope your 'fix' didn't just break it after all, lol.

Lol ok. I'll add them both in tonight :)