4 Oct 2011 12:32 PM #1
[4.0.6] DirectStore loadMask hacks bugging
There are some //hacks (I believe related to [EXTJSIV-3638]), which are not working well. - This was not issueing in 4.0.2a.
[strike]In my setup, I have an East Region holding 3 children with Flex. The 2nd child is a Grid with an autoLoaded DirectStore. There now is a mask that will not remove after the store has loaded. Also is it displaying (massive) mispositioning.[/strike]
I have no clue what's going on here
I can only remove the mask from the store if I call the mask() on it, and only then the unmask() works.
Even when overwriting these methods, its masking:
Ext.data.Store.prototype.mask = Ext.emptyFn;
Ext.data.Store.prototype.unmask = Ext.emptyFn;
I cannot provide code/testcase for this.
Last edited by robincasey; 4 Oct 2011 at 12:39 PM. Reason: Added unmask() then mask() infoonerror = setTimeout(Ext.emptyFn, Infinity)
4 Oct 2011 8:39 PM #2
- Join Date
- Apr 2007
- Sydney, Australia
- Vote Rating
I have no clue what's going on hereEvan Trimboli
Twitter - @evantrimboli
Don't be afraid of the source code!
4 Oct 2011 11:35 PM #3
The needed mask() call is needed as unmask() needs masked = true to be set. Somehow this seems not to be set in this case.
As the Store.js 4.0.6 code contains new //HACKS for loadMask support, I am trusting somebody will review these again.
I will later (shortly) look into a code example, but rather only spend time on this when this Ext code "looks final".onerror = setTimeout(Ext.emptyFn, Infinity)
13 Oct 2011 12:11 PM #4
FYI: I have borderLayout > collapsible east > collapsible gridpanel (2nd child of 3 flex items) > directstore with autoloadonerror = setTimeout(Ext.emptyFn, Infinity)