I don't think so... I'm not sure how splitting this up would help...I'd just end up scattering the stuff all over? It also seems like it would be a P.I.T.A. to have to manually select the correct view for 8 child components vs 1 call to an 'enhanced' state function that could 'run' multiple states on a single component.
I have multiple items that really 'feel' like they belong in the component: editable fields/display-only, saveButton/NoSaveButton, deleteButton/noDeleteButton, notes/noNotes, and updatedBy/updatedAt are some off the top of my head. So I'd end up with 6+ 'sub-components' for each form? Seems like it would get unwieldy quickly? Thinking about it - Flexbuilder could probably 'dummy it up' by generating all the view combinations, so that the standard player state functions would work. (hehe - a pure, brute force combinatorial approach would sure make for some large source files though :-P ) On 12/2/06, Mark Shepherd <[EMAIL PROTECTED]> wrote:
Each component (in other words, each MXML file, including the main application) can have its own states. So if your Notes area is in a separate MXML file, then it can have its own set of states. Same for any other discrete area of the screen that needs to have separate states. Does this help? Mark Shepherd Adobe FlexBuilder Engineering mark-shepherd.com
