I think the main reason I think I need to make my own TreeDataProvider is that the CF object persistence backend I'm integrating with requires that I send back deleted objects with a property, deleted=true. So there will be a bunch of objects which I don't want to show in my tree data with delete
TreeDataProvider is advanced stuff. Why do you think you need your
own? Give a little context and we'll see. We currently handle XML
and object graphs pretty well. Also the code for two
TreeDataProviders in shipped in Flash MX 2004 in
mx\controls\treeClasses
--- In flexcoders@yahoogroups.c
2 matches
Mail list logo
