djSeverin
22 Dec 2009, 11:08 PM
Update from ExtJS 3.0.3 to ExtJS 3.1.0 Supported release;
ExtJS connector.
-----------------------------------
I am currently stumped on the following problem and would love it if someone could give me some clues as to where to go looking to solve this one.
Our application uses a treeFilter that is filtering by date. This works just nicely in 3.0.3.
-----------------------------------
Using 3.1.0:
- The filter does work correctly on load;
- The filter fails when reload() is called no matter which node is selected;
- Resulting in the following error on the FireBug console:
When using ext-all.js:
- c.ui is null
- Ext.DomHelper=function(){var t=null,k=/^...dblclick",this.onNodeDblClick,this)}});\n
When using ext-all-debug.js:
- n.ui is null
- n.ui.show();\nIf "remove" is set to true when the treeFilter is instantiated, it will reload() without erroring; however, once a node has been filtered out of the tree, its gone for good. This behavior is exactly how remove should work; though I can't understand why: when "remove" is false, the above error occurs on refresh.
This will allow the root node to reload() without throwing an error:
this.viewFilter = new Ext.tree.TreeFilter(root.tree,{
autoClear : true,
remove : true
});This errors when root node is reload()ed:
this.viewFilter = new Ext.tree.TreeFilter(root.tree,{
autoClear : true,
remove : false
});Maybe the answer is right in front of me but I can't see it due to all these damned shiny christmas thingies strewn all over the office *rolls eyes* :-/
ExtJS connector.
-----------------------------------
I am currently stumped on the following problem and would love it if someone could give me some clues as to where to go looking to solve this one.
Our application uses a treeFilter that is filtering by date. This works just nicely in 3.0.3.
-----------------------------------
Using 3.1.0:
- The filter does work correctly on load;
- The filter fails when reload() is called no matter which node is selected;
- Resulting in the following error on the FireBug console:
When using ext-all.js:
- c.ui is null
- Ext.DomHelper=function(){var t=null,k=/^...dblclick",this.onNodeDblClick,this)}});\n
When using ext-all-debug.js:
- n.ui is null
- n.ui.show();\nIf "remove" is set to true when the treeFilter is instantiated, it will reload() without erroring; however, once a node has been filtered out of the tree, its gone for good. This behavior is exactly how remove should work; though I can't understand why: when "remove" is false, the above error occurs on refresh.
This will allow the root node to reload() without throwing an error:
this.viewFilter = new Ext.tree.TreeFilter(root.tree,{
autoClear : true,
remove : true
});This errors when root node is reload()ed:
this.viewFilter = new Ext.tree.TreeFilter(root.tree,{
autoClear : true,
remove : false
});Maybe the answer is right in front of me but I can't see it due to all these damned shiny christmas thingies strewn all over the office *rolls eyes* :-/