Oops... I misread the source code. Actually, in the one place where I had
used it it was bound to an implicit setter, like this:
private function set dataChanged(data:Object):void {
collectionData.refresh();
}
On Tue, Jul 22, 2008 at 2:48 PM, Troy Gilbert <[EMAIL PROTECTED]>
wrote:
> > You need to call collectionData.refresh() when the data property
> changes for
> > the itemRenderer. One way to do it would be:
>
> I always wonder what's the best practice for this. I would think that
> collections would have this built into them... why would one want to
> put a filter function on a collection and not use it when the
> collection was updated/changed? At the very least, it seems like a
> good candidate for a flag (refreshOnChange, for example).
>
> > <mx:Binding source="data" destination="dataChanged"/>
> >
> > then add the method:
> >
> > private function dataChanged(data:Object):void {
> > collectionData.refresh();
> > }
>
> I thought I had seen something like this but couldn't find a mention
> of it in the docs for the binding tag... so, destination can be a
> method that's called when data is changed? Does it need to be a setter
> (like BindingUtils)?
>
> Troy.
>
>
