-
12 Feb 2013 6:30 AM #1
[4.2.0.265] "selectionchange" is not fired
[4.2.0.265] "selectionchange" is not fired
The "selectionchange" event is not longer fired when selected records are removed from the store. It happens because the "removed" variable is not initialized with 0 but later is incremented with ++. It becomes NaN and "maybeFireSelectionChange" is never called.
Code from Ext.selection.Model:
Code:// @private // Called by subclasses to deselect records upon detection of deletion from the store deselectDeletedRecords: function(records) { var me = this, selected = me.selected, i, length = records.length, record, removed; // Deselect records which were removed for (i = 0; i < length; i++) { record = records[i]; if (selected.remove(record)) { if (me.lastSelected == record) { me.lastSelected = null; } if (me.getLastFocused() == record) { me.setLastFocused(null); } ++removed; } } if (removed) { me.maybeFireSelectionChange(true); } },
-
12 Feb 2013 6:55 PM #2Sencha - Senior Forum Manager
- Join Date
- Mar 2007
- Location
- St. Louis, MO
- Posts
- 33,684
- Vote Rating
- 435
Thanks for the report.
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.
Success! Looks like we've fixed this one. According to our records the fix was applied for
EXTJSIV-8602
in
4.2.0 Sprint 3.


Reply With Quote