This content has been marked as final. Show 5 replies
A ViewStack would suit this purpose fine. See the FB3 help doc or LiveDocs.
I did search and all I find are "states" written within the same application. I want to separate my code out and only use the application as a location where I call the form sitting in another folder. Maybe I don't know the term I should search? What would you suggest? Thanks.
Not being a .net programmer... not sure if this answers your question or not. :)
You could have a main mxml component with a view stack that is comprised of other mxml components. Those subcomponents could be in any folder you like as long as your project knows where to find them. So, for example, let's say you have main.mxml that has a ViewStack that references formA.mxml, formB.mxml, and formC.mxml. You'd have:
For more options check out TabNavigator and Accordion. These both eliminate the need for buttons with logic to navigate through the view stack.
Tab navigator is definitely a little easier but it all depends on how you want your UI to work. I use both a TabNavigator AND multiple ViewStacks (each tab) in one app.
"flex language reference viewstack" in Google, first result for API docs + example.