Hi Dustin, It's very gracious of you to offer, and I'd appreciate the help. However, I've 'worked around' this using 'copy and paste' coding to replicate the state info, and moving some of the button stuff out to the application bar. I really won't have anytime to spend on improving this till I get the rest of the app. in shape.
I'm not sure a 'snippet' will really work - because it only becomes valuable when you have lots of stuff to track... If it was just a 1 button sort of thing, you could just inline it. Let me see if I can come up with something. Steve On 12/3/06, Dustin Mercer <[EMAIL PROTECTED]> wrote:
Steve, I would love to help you with this, would you mind posting a small snippet of code that we can work with. I have some ideas to help simplify this, but want to make sure I understand exactly what you are working with before getting too detailed. You don't have to post anything too elaborate, just something small. I am thinking we can get a hybrid approach with binding / states to do what you want. I have had some situations like this arise as well, and that seemed to be the best way to get what I wanted. Dustin Mercer ------------------------------ *From:* [email protected] [mailto:[EMAIL PROTECTED] *On Behalf Of *Steve Hindle *Sent:* Sunday, December 03, 2006 1:56 PM *To:* [email protected] *Subject:* Re: [flexcoders] Re: Feature request? Ability to apply multiple states or views at once.. 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
