-
22 Jul 2011 9:29 PM #1
[4.0.2] one Store and two tree.Panel
[4.0.2] one Store and two tree.Panel
var tree_store = Ext.create('Ext.data.TreeStore', {
proxy: {
type: 'ajax',
url: '/data',
reader: {
type: 'json'
}
},
root: {
text: 'root',
expanded: true
}
});
tree1 = Ext.create('Ext.tree.Panel', {
store: tree_store,
width:300,
height:100,
renderTo: Ext.getBody()
});
tree2 = Ext.create('Ext.tree.Panel', {
store: tree_store,
width:300,
height:100,
renderTo: Ext.getBody()
});
This is a bug or what ? :]
When navigating one of the trees begin to happen strange things.
Expanding and collapsing part of the first panel action is executed on the second. Items disappear from the second tree and duplicate the first.
Sharing Store, it seems logical. It is possible?
-
24 Jul 2011 11:12 PM #2Sencha - Community Support Team
- Join Date
- Jan 2009
- Location
- Palo Alto, California
- Posts
- 1,941
- Vote Rating
- 6
Sounds like it to me, sending one of our support guys this way
Ext JS Senior Software Architect
Personal Blog: http://edspencer.net
Twitter: http://twitter.com/edspencer
Github: http://github.com/edspencer
-
25 Jul 2011 12:06 PM #3
Confirmed as a bug and opened a ticket
-
8 Sep 2011 6:17 AM #4
I've also encountered this problem and there are additional strange behaviors like auto-scrolling doesn't work in the second tree and both trees will suddenly stop expanding and collapsing nodes. In my case, the trees are on a menu invoked from a button. Has the bug been targeted for a release? Is there a workaround?
-
8 Sep 2011 9:16 AM #5
I just checked the ticket, and it has not been scheduled for a release yet. If a workaround becomes available, I will post it to this thread.
-
3 Nov 2011 8:40 AM #6
Why was this thread marked as fixed? I experience the same problem (using ExtJS 4.0.7)! Collapsing & Expanding causes the items in "Exclusion masks" jump to the upper tree. Also when I change checkboxes in the upper tree, the changes are reflected in items of the lower tree instead of the upper one.
2trees1store.jpg
-
3 Nov 2011 9:21 AM #7
The fix didn't make it into 4.0.7. It will be in 4.1.0.
-
3 Nov 2011 11:43 AM #8
-
17 Jan 2013 1:40 PM #9
Is it fixed in ExtJS 4.1 ? I am still seeing this behavior in ExtJS 4.1.1a release.

Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-3571
in
4.1.


Reply With Quote