-
14 Jul 2011 11:40 AM #11
alexmace has a point
alexmace has a point
Tree filtering is completely absent. There is expectation that tree filtering be implemented to some degree. That is the difference between open source and paid for products. Keep it on your radar, to-do list, write it on your hand, whatever.

-
14 Jul 2011 11:41 AM #12
-
18 Jul 2011 12:26 PM #13
surprised when I found filtering is missing in 4.0.2. I should double check before answering my supervisor that extjs4 CAN do filtering on tree.
now, I am screwed.
"on radar"? It doesn't make any sense. Is this a feature sencha going to build or not? If you are going to build it in 4.x, when? timeline?
-
21 Jul 2011 6:05 AM #14
-
21 Jul 2011 7:04 AM #15
?
?
I think we will have to roll our own since this was closed and they remain silent. I might look to the 3.x code to bolt-on what was done before, however, I get the feeling that there was an architectural change that completely broke the previous solution.

-
11 Aug 2011 11:51 PM #16
So.....will tree filtering make it to Ext 4.1?
Thnks
-
29 Feb 2012 5:31 PM #17
Need update
Need update
I am trying to migrate to 4.1 and still can't seem to find any ability to filter trees. I have already put in weeks of work to migrate our app in Ext 4 and now come to find that this is a missing functionality.
Please provide some sort of an answer as to what the status of this issue is so we can take appropriate action.
Thanks.
-
29 Feb 2012 11:31 PM #18
Well, I do have a crude implementation (not complete though). It currently has the following limitations
1. The tree must be fully loaded. I call expandAll on the root. Not sure if that will load nodes that have not been loaded
2. It does not correctly hide all the empty folders (will be looking into that sometime this month). It does show the correct nodes but I think somewhere in the algorithm, it fails to recognize some of the folders
3. It only works as expected when animations are off. I usually get dom exception errors when animations are on.
If 1 is not a problem, I could try and correct the 2nd limitation.
Currently performance is ok with the max of 250 nodes I tested it with.
Thank you for reporting this bug. We will make it our priority to review this report.
Similar Threads
-
[CLOSED] Ext JS Tree x-tree-node-over stuck after clicking node
By noriak in forum Ext 3.x: BugsReplies: 2Last Post: 23 Dec 2010, 2:36 AM -
[CLOSED-874] Tree nested node.select() method fails when given node is first rendered
By albeva in forum Ext 3.x: BugsReplies: 1Last Post: 20 May 2010, 9:06 AM -
[CLOSED] The parent of selected tree node is NULL in Async Tree
By fangning in forum Ext GWT: Bugs (2.x)Replies: 3Last Post: 10 Nov 2009, 12:15 AM -
[CLOSED] Problem Deleting a Tree Node
By Seasnark in forum Ext 2.x: Help & DiscussionReplies: 3Last Post: 26 Jul 2009, 9:19 AM -
[2.2][CLOSED] Ext.Tree node not closable
By Northrog in forum Ext 2.x: BugsReplies: 2Last Post: 16 Sep 2008, 9:57 PM


Reply With Quote