The reason for doing this is because ultimately all viewstates in a component are based on the base state, so it becomes more efficient when changing into all those other viewstates that do not contain the children listed in the base state:
"When Flex changes to the new view state, it restores the base state, applies any changes from the state determined by the basedOn property, and then applies the changes defined in the new state." http://livedocs.adobe.com/flex/3/html/using_states_3.html --- In [email protected], "chigwell23" <[EMAIL PROTECTED]> wrote: > > Several examples are coded where the Main.mxml base state is empty and > there is a child state called e.g. main App (start) containing the > initial gui components. (Examples are based on the Flex multi-window > architectures). > > Does this make cleaner coding? Because one could obviously jump > straight into things without the extra child state? TIA. > > > > <mx:Application > ....... > > > <mx:states> > <mx:State name="mainApp"> > <mx:AddChild position="lastChild"> > <comp:WindowedApp top="0" left="0" right="0" bottom="0"/> > </mx:AddChild> > </mx:State> > </mx:states> > </mx:Application> > > as compared to > > <mx:Application > .....> > > <comp:WindowedApp top="0" left="0" right="0" bottom="0"/> > > </mx:Application> >
