gordon-robinson
27 Sep 2007, 10:31 AM
Just been caught by this.
Sorry if it's been reported before, I didn't see in any threads.
TreeNode's removeChild method looks immediately for
ownerTree, which does not exist until the tree has been rendered.
Other methods seem to check for ownerTree before following it.
removeChild : function(node){
this.ownerTree.getSelectionModel().unselect(node);
Ext.tree.TreeNode.superclass.removeChild.apply(this, arguments);
Sorry if it's been reported before, I didn't see in any threads.
TreeNode's removeChild method looks immediately for
ownerTree, which does not exist until the tree has been rendered.
Other methods seem to check for ownerTree before following it.
removeChild : function(node){
this.ownerTree.getSelectionModel().unselect(node);
Ext.tree.TreeNode.superclass.removeChild.apply(this, arguments);