You can also create state objects on-the-fly with ActionScript. This
allows you to paramatise the 'state of the state', which might be a
more concise way to manage this task. Create / instantiate / modify
your existing state object, then set it to be current.
On 03/12/2006, at 11:04 AM, Steve Hindle wrote:
Hi Dustin,
It's 'based on' that actually 'teased' me with this...
As you start having more 'optional' things in the component
('noNotes','noSaveButton',etc), you end up with a 'states
explosion'...
'based on' gets about half-way there, so I figured it could be
enhanced to handle the rest?
I could do it all by manually adding/removing child components, but
that seems like overkill.
Thanks!
