-
24 Jan 2013 7:00 AM #1
EXT 4.1.3: error when removing nodes from tree
EXT 4.1.3: error when removing nodes from tree
I try to remove a node from a tree
node = tree.getRootNode().findChild("id", "myId", true);
node.remove(true);
This produces an error in Ext.data.Model (the red line)
The error occurs because store is of type TreeStore, and TreeStore does not have a remove function. It inherits from AbstractStore and the remove function is added in Store.When I remove the boolean (node.remove(false)) then there's no error, but the node is kept in the store...
This error did not occur in Ext 4.1.1
callback = function(operation)
{
args = [me, operation];
if (operation.wasSuccessful()) {
for(storeCount = stores.length; i < storeCount; i++)
{ store = stores[i];
store.remove(me, true);
if (isNotPhantom) {
store.fireEvent('write', store, operation);
}
}
me.clearListeners();
Ext.callback(options.success, scope, args);
} else
{
Ext.callback(options.failure, scope, args);
}
Ext.callback(options.callback, scope, args);
};
Any help would be appreciatedCaius CaesarLast edited by Caius Caesar; 24 Jan 2013 at 7:04 AM. Reason: missing linebreaks
-
24 Jan 2013 7:37 AM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,617
- Vote Rating
- 435
Have you tried with 4.2?
Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Forum Manager
________________
http://www.JSONPLint.com - Source to lint your JSONP!
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
https://github.com/mitchellsimoens
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services services@sencha.com
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is almost in print!
When posting code, please use BBCode's CODE tags.
-
24 Jan 2013 7:47 AM #3
No, didn't realize it was out there. It's still in Beta, isn't it?
We have a big app in the making and experience some issues with every Ext upgrade. We moved just yesterday from 4.1.1 to to 4.1.3. and we can't afford to upgrade the minute there's a new version out.
Having said that, we do make an effort not to stay behind too far, so when 4.2 is released, we will try it and upgrade quickly, if there are no issues.
In the meantime...
What about the bug. It looks like an outright omission to me. Will there be some sort of patch?
Regards,
Caius Caesar
Wait! Looks like we don't have enough information to add this to bug database. Please follow this template bug format.


Reply With Quote