True. In my own code I would always explicitly name a state and set that as the default. It creates less confusing code, especially if you're going to be returning to that state elsewhere in the program. Setting currentState = null or currentState = "" is more confusing than naming a state "default" and referring to it as such. It also guards against possible changes in the out-of-the box behavior of the view states.
Not saying it's the right way or the only way, but to me it appears to be the more maintainable way. >But what if I /want/ the current state to be the default? <mx:Application >currentState="" > doesn't do it.. I still need the logic from Jeff H. > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:3521 Subscription: http://www.houseoffusion.com/groups/Flex/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.37
