A ViewStack is simply a way to switch between components. It has no visible presence of its own. The children of a ViewStack can be anything (in some container), including a full TabNavigator. You can nest ViewStacks as desired.
A side note on TavNavigator; if you think you will ever want to dynamically control the visible tabs, say based on user identity/permissions, I advise TabBar + ViewStack. To remove hide a tab in a TabNavigator, you have to manipulate the childen directly. If you use a TabBar, you can control its content just by manipulating its dataProvider. A hidden view will still be in the ViewStack, but its tab will not be visible, thus the view will be unavailable. Tracy Spratt, Lariat Services, development services available _____ From: [email protected] [mailto:[email protected]] On Behalf Of Penny Laus Sent: Saturday, January 23, 2010 2:06 AM To: [email protected] Subject: [SPAM] Re: [SPAM] [flexcoders] TabNavigator switches to second tab when revealed after a currentState change On Sat, Jan 23, 2010 at 5:28 PM, Tracy Spratt <tr...@nts3rd. <mailto:[email protected]> com> wrote: For a change as significant as that, I suggest using ViewStack instead of states. Tracy, Thanks very much for responding - I always read your postings with attention. In my case are you suggesting I put everything into a ViewStack and not use states? So, I'd have something like ViewStack 0 - My landing screen with the login/send password/add registration 1 - 2 -3 My registration details Am I right in thinking that I could use a TabBar to make ViewStack 1, 2 & 3 look and act like a TabNavigator? Thanks for the help!
