Thanks for your response
There is no datatype of the data provider, it's just a tree of generic objects
of type TreeItem. Following is the signature of the TreeItem class:
import mx.collections.ArrayCollection;
import mx.collections.IViewCursor;
public class TreeItem {
[Bindable]public var id : String;
[Bindable]public var label : String;
[Bindable]public var type : String;
[Bindable]public var children : ArrayCollection = null;
[Bindable]public var description : String;
}
The "children" attribute will contain the leaf nodes of the tree and the nodes
are also of type TreeItem.
Also, I don't hahve any gett or set methods for the member attributes because
the attributes are themselves declared as "public" .
Thanks !
--- In flexcoders@yahoogroups.com, "Tracy Spratt" <tspr...@...> wrote:
>
> Typically this happens when you update the dataProvider with low-level
> assignments, instead of using the API.
>
>
>
> Exactly what is the datatype you your dataProvider?
>
>
>
> Tracy Spratt,
>
> Lariat Services, development services available
>
> _____
>
> From: flexcoders@yahoogroups.com [mailto:flexcod...@yahoogroups.com] On
> Behalf Of Madhav Annamraju
> Sent: Sunday, March 29, 2009 7:48 PM
> To: flexcoders@yahoogroups.com
> Subject: [flexcoders] Explicit refresh in a data control
>
>
>
>
> Hello Flex community,
>
>
>
> I have a problem with refreshing data in a list control when the data
> provider is a tree structure of generic objects. Here is the situation -
>
>
>
>
>
> Consider that I have a class called TreeItem with the following attributes.
>
>
>
> Class TreeItem
>
> {
>
> public var name:String;
>
> public var description:String;
>
> publilc var image:String;
>
> public var children:TreeItem;
>
> }
>
>
>
> A tree structure of this TreeItem is provided as a data provider to a list
> control.
>
> Issue is that the list control is not reflecting changes in the tree
> structure when an attribute of TreeItem is updated even though I am using
> data binding to bind TreeItem to the list control.
>
> I was wondering if there is a way to explicitly trigger a refresh. I have
> already tried doing this by raising event PropertyChangeEvent but this is
> not making any difference. Appreciate if you can share your thoughts on
> this.
>
