> wouldn't binding the component to a selectedStates > property on the model cause all instances of the component to reflect > one of it's sibling's data??
Yes. :-) I assumed that you had only one dropdown and that you wanted selectedStates to be reflected throughout your app. In this case I'd probably move towards storing this data and logic in my view. There are probably lots of different ways you could do this but if you have things set up so that three instances of a specific component each contain a dropdown / dragToArea pair, that component would be a logical place to put your lists and your logic... Other thoughts, anyone? Douglas ------------------------------------------------- Douglas McCarroll CairngormDocs.org Webmaster http://www.CairngormDocs.org Flex Developer http://www.brightworks.com 617.459.3840 ------------------------------------------------- lostinrecursion wrote: > > Douglas, > > Thanks for your concise and clear reply. Much appreciated. One thing > is a little confusing though. > > >From your post: > > If you want to follow this approach in your app you might do something > > like the following: Create an object on the model that keeps track of > > selectedStates list and also maintains a displayStatesUS list in > > addition to your STATES_US constant. Every time the user drags a state > > have a command call a method on this object, which updates these two > > properties. Bind your dropdown to displayStatesUS. > > That really wouldn't be effective though. Since the component in > question is used in various places across the application (For > example, in one instance it is on the same view in 3 places for > different fields), wouldn't binding the component to a selectedStates > property on the model cause all instances of the component to reflect > one of it's sibling's data?? > > Thanks so much. While I'm not new to Flash/Flex, etc, I am very new to > the proper development of things. ;) > >
