This seems to have done the trick. Thanks guys.
It’s okay to put composer.removeHidden in main.lua. When using Composer (or previously Storyboard), main.lua is a place to initialize every thing. Since it’s not a scene, you won’t be going back to it. You can load sounds that you want all the time, initialize ads or in-app purchases, put in your facebook.init() etc. As such main.lua will frequently contain all of the listener functions for these items. You can set up any hardware listeners, like key listeners, tilt events etc.
Since composer.removeHidden is a setup feature it’s fine to put in main.lua. Then at the end of your main.lua you do a gotoScene() to your first scene and from then on your app bounces between the various scenes.
One slight exception this (but not really when you think about it) is building a tabBar based app. In Corona any display objects that are not inserted into a scene, stay on top of the scenes. You can create your widget.newTabBar() in main.lua and have each tab load a scene. You don’t really go back to main.lua, but the tabBar has the statements to change scenes (Like in the Business App Sample (https://github.com/coronalabs/business-app-sample).
Rob
OK thanks for all of the info, I appreciate your time, I know you guys are busy.
That is good to know. I will definitely take another look at the business app sample.
Are all the sample apps up to date (for instance: Graphics 2.0, composer, etc.) ?
Cheers!