I wasn't correct.
Column.itemRenderer.properties will not work.
--- In flexcoders@yahoogroups.com, "markgoldin_2000"
<[EMAIL PROTECTED]> wrote:
>
> How about something like this.
> //Add lsitener to your primary combobox:
> addEventListener("change", handleDataChanged);
> public function handleDataChanged(event:ListEvent):void
> {
> var Column:AdvancedDataGridColumn = new AdvancedDataGridColumn;
> Column = AdvancedDataGrid(listData.owner).columns[someIndex];
> // your condition to enable/disable, then
> Column.itemRenderer.properties = {enable:true};
> }
> If you want to do more then just enable/disable second combo then
you
> could have created a setter on your secondary combobox:
> public function set setSomething(someData:XMLList[example]):void
> {
> //do something on your secondary combobox like
> enable = true; // under your condition
> }
> and then the line:
> Column.itemRenderer.properties = {enable:true};
> might look like this:
> Column.itemRenderer.properties = {setSomething:paramerData};
>
> Something alone these lines.
>
> --- In flexcoders@yahoogroups.com, "quantum_ohm" <charly.antoine@>
> wrote:
> >
> > Hi Alex, thx for responding !
> >
> > Is there a particular sample on your blog which will be close to
> what
> > I'd like to do ?
> > I've check out your blog, but I get lost with all the samples...
> >
> > Regards.
> >
> > --- In flexcoders@yahoogroups.com, "Alex Harui" <aharui@> wrote:
> > >
> > > Normally, everything should be data-driven. The first combobox
> changes
> > > a property in an item in the dataprovider and the second
combobox
> is
> > > refreshed and sees that it changed and enables itself. You can
> examine
> > > some of the examples on my blog (blogs.adobe.com/aharui). They
> aren't
> > > exactly what you're looking for, but show how the visuals can
> respond to
> > > changes to the dataprovider items.
> > >
> >
>
