30 Nov 2012 8:15 AM #1
Answered: Moving the roweditor to another grid
I have a grid that is supposed to have a variable number of columns, which the user can change (a "dynamic" grid). This means 1) column model comes from the server and 2) I have to recreate the grid each time. Destroying the old grid doesn't get rid of the roweditor, perhaps because we have saved the grid config, and since (previously) we reuse the config, the roweditor gets reapplied, but to a different grid, causing errors. To solve that error, we have it recreate the editor every time. If it is efficient, I'd like to keep the roweditor, since I think it would lower the recreation time. Hopefully, your eyebrows aren't raised anymore.word
IMO, each grid should use it's own row editor instance. The grid should be destroying the classes it uses including the row editor instance.
3 Dec 2012 4:49 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
IMO, each grid should use it's own row editor instance. The grid should be destroying the classes it uses including the row editor instance.Mitchell Simoens @LikelyMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
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 firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.