-
9 Jul 2009 2:56 PM #11
Hi Condor,
Many thanks for the Ext! This is exactly what i needed after struggling with huge xml file.
Here it's in action:
http://dev.sk-typo3.de/cetest/svn-log.htmlvg Steffen
--------------------------------------
Release Manager of TYPO3 4.5
energlobe.de - german online magazine
-
9 Jul 2009 4:11 PM #12
You missed out the change from
toCode:onRefreshClick
Ext.PagingToolbar doesnt have a onRefreshClick function.Code:refresh
I also found another bug,
should beCode:destroy: function() { if (this.storeId) { Ext.PagingStoreMgr.unregister(this); } this.data = this.allData = this.snapshot = null; Ext.destroy(this.proxy); this.reader = this.writer = null; this.purgeListeners(); },
Code:destroy: function() { if (this.storeId) { Ext.StoreMgr.unregister(this); } this.data = this.allData = this.snapshot = null; Ext.destroy(this.proxy); this.reader = this.writer = null; this.purgeListeners(); },
-
9 Jul 2009 11:24 PM #13Sencha - Community Support Team
- Join Date
- Mar 2007
- Location
- The Netherlands
- Posts
- 24,251
- Vote Rating
- 41
Both fixed.
-
16 Jul 2009 5:00 AM #14
grouping compatible version of PagingStore
grouping compatible version of PagingStore
Hi:
Are there any plans to make a grouping compatible version of this?
Or, any pointers on how you might go about providing client-side paging with/grouping?
Thanks,
Lee Wexler
-
16 Jul 2009 5:24 AM #15
grouping compatible version of PagingStore
grouping compatible version of PagingStore
Just saw your comment in the 2.0 thread, re: grouping. I will try it.
Sorry for the noise, and thanks for this!
-
29 Jul 2009 11:29 PM #16
grouping compatible version of PagingStore
grouping compatible version of PagingStore
The Grouping Store variant worked for me as well with Ext-JS 3.0 PagingStore.
Thanks!Code:Ext.ux.data.PagingGroupingStore = Ext.extend(Ext.ux.data.PagingStore, { remoteGroup: Ext.data.GroupingStore.prototype.remoteGroup, groupOnSort: Ext.data.GroupingStore.prototype.groupOnSort, clearGrouping: Ext.data.GroupingStore.prototype.clearGrouping, groupBy: Ext.data.GroupingStore.prototype.groupBy, applySort: Ext.data.GroupingStore.prototype.applySort, applyGrouping: Ext.data.GroupingStore.prototype.applyGrouping, getGroupState: Ext.data.GroupingStore.prototype.getGroupState });
-
30 Jul 2009 11:34 PM #17
-
4 Aug 2009 12:05 AM #18
In 3.0, PagingStore and GridFilter cuase problem in PagingToolbar
In 3.0, PagingStore and GridFilter cuase problem in PagingToolbar
I am using the newest PagingStore v0.4 and gridFilter 0.2.8. I have problems on the paging toolbar.
Two problems I've noted:
1. Page count always keeps the same as well as total records count on the paging toolbar.
2. Store shows current empty page instead of navigating to 1st page (if I filter 1 record for example)
Should I fire some event? where do I fire?
thanks
-
4 Aug 2009 12:53 AM #19
another page nation problem
another page nation problem
let's say I have 3 total pages. Currently, I am in page 2.
I click the refresh button which I override
Ext.override(Ext.PagingToolbar, {
// private
refresh: function(){
this.store.loadData(newObj);
}
});
the grid reloads and show the correct records of the second page since i di not change the lastoptions.start and limit. However, the paging toolbar shows I am in page 1.
I must miss something between the page store and page toolbar. Can some one please help me. thx
-
4 Aug 2009 2:30 AM #20Sencha - Community Support Team
- Join Date
- Mar 2007
- Location
- The Netherlands
- Posts
- 24,251
- Vote Rating
- 41
loadData will fire a load event without start and limit parameters, making the PagingToolbar think it is on the first page.
Instead of loadData try:
Code:var r = store.reader.readRecords(data); store.loadRecords(r, Ext.apply({}, store.lastOptions), true);


Reply With Quote
