I usually ignore the base state, or at the least only put things in it that are shared by the entire application. I suppose now that I think about it I've never had a situation where the base state contains everything needed for a state the user would actually use. Every Flex application I've built so far contains a login state, so my approach has been one of necessity in that the login state contains only a login form and no other portions of the application.
I personally don't like the idea of setting currentState to anything other than a specifically named state for reasons of clarity. If I had a situation where I wanted to navigate to the base state I'd probably create an empty child state, name it, and set currentState to that child state. Some developers might find that as confusing as I find setting currentState = null in order to get to a specific destination :) I'm not saying that you or anyone else is wrong - I've been in this game long enough to know that 'right' and 'wrong' really mean gray and grayer :) It's only which approach creates less confusion for the developer(s) who have to maintain the code and that's a matter of opinion. >I didn't think you can name the Base State. Are you saying I'm >wrong, or that you ignore the 'base' state and create a named state >as the default? > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Upgrade to Adobe ColdFusion MX7 Experience Flex 2 & MX7 integration & create powerful cross-platform RIAs http:http://ad.doubleclick.net/clk;56760587;14748456;a?http://www.adobe.com/products/coldfusion/flex2/?sdid=LVNU Archive: http://www.houseoffusion.com/groups/Flex/message.cfm/messageid:3530 Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
