[flexcoders] Re: Best Practice for Subclassed UIComponent and DataProvider

2011-08-29 Thread hanzo55
just inject a reference to the facilities model where needed, and hook it up to the combo box. That would be best practice. But, at the end of the day, the goal is to make it work, so... -TH --- In flexcoders@yahoogroups.com, hanzo55 shawn.a.holmes@ wrote

[flexcoders] Re: Best Practice for Subclassed UIComponent and DataProvider

2011-08-27 Thread hanzo55
the dataProvider to the model's property, the binding problem is probably upstream from the combo box. Good luck Shawn, just trying to help. -TH --- In flexcoders@yahoogroups.com, hanzo55 shawn.a.holmes@ wrote: There's more to the story in regards to the class design than what's

[flexcoders] Re: Best Practice for Subclassed UIComponent and DataProvider

2011-08-26 Thread hanzo55
by then. On 8/25/11 9:41 AM, hanzo55 shawn.a.holmes@ wrote: I am working with a project already in place. It uses Cairngorm and is built on Flex 3.0.2.2113 A standard ComboBox is implemented in one of the views like so: mx:ComboBox dataProvider={model.facilities} id

[flexcoders] Best Practice for Subclassed UIComponent and DataProvider

2011-08-25 Thread hanzo55
I am working with a project already in place. It uses Cairngorm and is built on Flex 3.0.2.2113 A standard ComboBox is implemented in one of the views like so: mx:ComboBox dataProvider={model.facilities} id=Facility model is a bindable singleton, and one of its properties, facilities is a public