Load tree using renderer

Question

Hi,
My current application contains a <mx:tree>
his dataprovider is an xml file loaded from a httpservice
this tree have a renderer extends TreeItemRenderer that allow me to add checkbox when node doesn't have childs.
When user check or uncheck a node, i put some information in a datagrid.
This datagrid is finally export to a file.
Now the question is how can i initialize the tree using the two file (the original and this saved) ?
See below my renderer code :
package manageCheckBox
import flash.events.Event;
import flash.events.MouseEvent;
import mx.collections.IViewCursor;
import mx.controls.Alert;
import mx.controls.CheckBox;
import mx.controls.DataGrid;
import mx.controls.treeClasses.*;
import mx.controls.treeClasses.TreeItemRenderer;
public class DisplayCheckBox extends TreeItemRenderer{
public var chk:CheckBox;
public var itemXml:XML; // original xml file
public var dg:DataGrid; // datagrid to put information on
public var myFields:XML; // saving file
public function DisplayCheckBox(){
super();
mouseEnabled = false;
override public function set data(value:Object):void{
if(value != null){
super.data = value;
this.itemXml = XML(value);
if(this.itemXml.@checked == "1"){
this.chk.selected = true;
}else{
this.chk.selected = false;
override protected function createChildren():void{
super.createChildren();
chk = new CheckBox();
chk.addEventListener(MouseEvent.CLICK, handleChkClick);
addChild(chk);
override protected function updateDisplayList(unscaledWidth:Number, unscaledHeight:Number):void{
super.updateDisplayList(unscaledWidth,unscaledHeight);
if(super.data){
var tld:TreeListData = TreeListData(super.listData);
if(tld.hasChildren){
this.chk.visible = false;
}else{
this.chk.visible = true;
if(chk.visible){
this.chk.x = super.label.x
super.label.x = this.chk.x + 17;
this.chk.y = super.label.y+8;
private function handleChkClick(evt:MouseEvent):void{
if(this.chk.selected){
this.itemXml.@checked = "1";
// put information on the datagrid
dg.dataProvider.addItem(
"col1": this.itemXml.@label,
"col2": this.itemXml.@label,
"col3": this.itemXml.@resourceId
}else{
//this.checked = false;
this.itemXml.@checked = "0";
var vObject:Object = dg.dataProvider ;
var cursor:IViewCursor=vObject.createCursor();
while( !cursor.afterLast )
if(cursor.current.col1 == this.itemXml.@label) {
cursor.remove() ;
cursor.moveNext();
Thanks in advanc for your reply,
Regards,
HadanMarv

Answer 1

A) The tree region is not refresh-enabled. If you want it to act on any change in session state the page will always have to be submitted/reloaded to reflect those changes.
B) Providing a where-clause to the tree query is not done. There is nothing to achieve by doing so because of the nature of the query: the connect by occurs before the where clause filtering. You will break any and all metadata for the whole tree construct to use.
Consider nodes which are from a different department than the one you filter on: how would the tree have to be constructed? What if a parent node misses because of that? How would it's child nodes match up? Worse: what if you select a dept which does not belong to the root node? The root node would not be displayed and subsequently no child nodes would be shown. Simply because the generated meta-data does not match up.
Eg if "BLAKE" would be "SALES" and "JAMES" would be "ACCOUNTING", and you filter on dept = "ACCOUNTING", then "BLAKE" would be gone... But "JAMES" too. Just to illustrate how the represented data would be wrong.
There is a reason the tree query requires the addition of the LEVEL pseudo-column, as this is used to iterate over the data to provide to the tree. You can see how horribly a where clause breaks that mechanism by simply running the query in sql developer or the sql workshop.
tldr; Don't.