5 Nov 2012 11:46 AM #21
Is your Solution available?
7 Nov 2012 4:34 AM #22
7 Nov 2012 9:18 AM #23
thanks, i will try it...
currently i use my own provider without buffering. While reading your code i found a little problem:
me.store.find('name', name), row;
me.store.findExact('name', name), row;
When using this this kind aof states store.find give the wrong position when searching for 'ext-dashboard'...
8 Nov 2012 9:53 AM #24
I will investigate this tomorrow or next week, but it seems that you have found a bug. Congrats. Issue #3 if you want to track it.
1 Aug 2013 5:13 AM #25
1. Lock any of the column in the GRID.
2. Reload the Grid.
3. ExtJs internal error on console and GRID failed to load.
Please tell me the solution for that. Thanks in advance.
1 Aug 2013 5:17 AM #26
I'm currently not using the locking feature. Could you provide a small test? You can use Sencha's brand new Fiddle if you like: https://fiddle.sencha.com/#home
Tip: Because of some issues with raw data of GitHub, it is possibly required to replace a raw url like https://raw.github.com/hlsolutions/e...ttpProvider.js to http://rawgithub.com/hlsolutions/ext...ttpProvider.js
1 Aug 2013 5:37 AM #27
Thanks for reply.
You can test it at your own end as well. Just add "locked: true" to any of the COLUMN of the GRID. Then you can see LOCK and UNLOCK option in the column property (Just below the column hide/show).
After that you can see Lock/Unlock state in not maintained.
1 Aug 2013 5:59 AM #28
1 Aug 2013 11:44 PM #29
Issue with Ext.state.CookieProvider
It is also having issue with Ext.state.CookieProvider. Locking and Unlocking State is not persists even by using Ext.state.CookieProvider. I think it is the ExtJs issue.
If anybody has any workaround for this, then please let me know. Thanks
9 Oct 2013 6:57 AM #30