-
14 Jan 2013 2:04 PM #1
[4.2.0.265 Beta] Event signature changed: Ext.data.TreeStore.beforeappend
[4.2.0.265 Beta] Event signature changed: Ext.data.TreeStore.beforeappend
Until Ext JS 4.1, the signature of the event Ext.data.TreeStore.beforeappend is [ this, node, eOptions ] where you can use this as the parent of node. So, 3 arguments.
Now trying 4.20.265 beta, the signature has changed to [ [parent, node], eOptions] (2 arguments, where the first is an array). I would suggest that something there is a tiny change (typo?) when applying arguments to the event callbacks..?
Either this is a documentation bug or an internal "bug".
Do you need more information about this issue? Personally, I think that should be sufficient.
-
14 Jan 2013 2:34 PM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,666
- Vote Rating
- 435
Thanks for the report! I have opened a bug in our bug tracker.
-
14 Jan 2013 2:39 PM #3
Are you sure?

Those first two args are the node appended to, and the node being appended.Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
-
16 Jan 2013 1:58 PM #4
Yes.
I've made a test case, take index.js and and index.html from this commit: https://github.com/knalli/extjs4-demos/commit/0602ef202c66e10e9462f7cf473768caa416245f
See my output (Chrome24 OSX): Bildschirmfoto 2013-01-16 um 22.57.40.png
I hadn't checked this correctly: it is only the first call which is unsual (but the first which breaks my app).
Perhaps a different handling when applying the root node?
-
16 Jan 2013 11:07 PM #5
Ah! Well spotted! It's the append of the root node. All others are correct.
Search the forum: http://www.google.com/coop/cse?cx=01...%3Az7of1ufqccu
Read the docs too: http://extjs.com/deploy/dev/docs/
Scope: http://extjs.com/forum/showthread.ph...642#post257642
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-8232
in
4.2.0 Sprint 3.


Reply With Quote