Ok, if you don't mind, I'd like to extend on that a little. Most of
the LIst boxes allow for multiple selections. Since when I set the
selectedItems property it stores an Array with Obj references (i.e.
0:N{label: 'blah', data: 'some data'}) - how can I extract only the
data properties since that is all that needs to go back to the server?I know that I could: a) Loop over the structure on the client and do it manually. But I have up to 20 fields that behave this way in one screen. That could be a mother load of loops and processor time, regardless of Flash 9's new engine. b) Pass all the data back to the CFC as it is and do the work of extracting there. But now, not only do we have server loops, the Business tier has to have specific knowledge of the Client. Clearly, a big no no. Meaning that, in order to get just the data properties in CF I would have to specifically reference them in my CFC code. is there a simpler way to store only my data values. The labels are no longer needed once they are loaded in. They are purely visual. All the data fed back is just numbers (Id properties) Thanks for any help you can offer. Damn I hope that someday I can be as wise as some of the people on here so that I could help a new guy like me. ;) -Kenny --- In [email protected], "Oriol Gual" <[EMAIL PROTECTED]> wrote: > > HI Kenny, > > There is a much more easier way. I suppose you have your OptionVO in your > model. Then you only have to do this: > > <mx:List id='myList' change={model.optiopnvo = OptionVO(myList.selectedItem)}/> > or whatever you want: > > <mx:TextInput id="myText" change="{model.optionvo.propertie = myText.text > }"/> > > > Remember to import the ModelLocator in your mxml file and get an instance of > it. > > Oriol. > > > 2006/8/27, lostinrecursion <[EMAIL PROTECTED]>: > > > > It's so simple, I can't believe I didn't see it before. > > > > One event and One command can do the work of updating the ValueObject > > for my Product. All the event has to carry is the property name it > > will update and the value. The format of the value is known to the > > Model and doesn't need to be known to the View. So, when it > > dispatches, it just puts things where they go. > > > > If you know of a better way, let me know. That sounds like good old > > MVC/Cairngorm to me! > > > > -Kenny > > > > > > > > > > > > > > -- > > Flexcoders Mailing List > > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
