Well, I suppose I could, but that doesn't seem like an appropriate use of states to me. I could be wrong though. Do states use deferred instantiation? There will eventually be several sets of screens and most users will only ever use one. I would like to refactor to Modules eventually, so I'm also looking for a solution that will translate to that fairly painlessly.
Thanks, Ben --- In [email protected], "Erik Price" <[EMAIL PROTECTED]> wrote: > > On 4/30/07, ben.clinkinbeard <[EMAIL PROTECTED]> wrote: > > > Basically, when the user selects a certain task, I need to attach a > > set of screens to the stage and allow them to begin working. If they > > later choose a different option, I need to remove the existing stack > > and attach the new one. > > I don't know enough about Cairngorm to say whether this would work > with that framework, but is this something that States can help you > with? I.e., databind the states to the user's task selection in the > UI, and add the appropriate children to the display list in that > state? This would let you keep your view code in the view and not > pollute your command.... > > <http://livedocs.adobe.com/flex/2/docs/00000924.html#391089> > > e >
