Ext.ux.data.PagingStore [v0.5]

[Condor]

Yes, 'start' and 'limit' are integer parameters (both PagingStore and PagingToolbar do some math with them).

[diablo]

hi Condor,

I have the following situation. A tab panel that holds 2 grids, one using pagingstore and the other one normal store. When I am accessing functions (i.e. loadRecords() ) for the grid with normal store, the store is a instance of PagingStore, used in the first grid. Is there a way to avoid this? Comes this from that PagingStore extends Store?

Thanks!

[Condor]

Yes, v0.5 creates PagingJsonStore etc. wrong, which in turn affects Ext.data.Store. I still need to create a v.0.5.1 for that...

If you're in a hurry: the fix is somewhere in this thread.

[diablo]

Yes, v0.5 creates PagingJsonStore etc. wrong, which in turn affects Ext.data.Store. I still need to create a v.0.5.1 for that...

If you're in a hurry: the fix is somewhere in this thread.

thanks for the quick reply. If you are referring to the solution povided by @3dm with reverting to constructor to v0.4.1 i have tried it but unfortunatly it doesn't work for me.

[Condor]

thanks for the quick reply. If you are referring to the solution povided by @3dm with reverting to constructor to v0.4.1 i have tried it but unfortunatly it doesn't work for me.

Yes, that was the fix I was referring to.

If that doesn't help you must be having a different problem. Can you post an example?

[diablo]

Yes, that was the fix I was referring to.

If that doesn't help you must be having a different problem. Can you post an example?

Hi Condor. Sorry for the late response. In my case made more sense to switch the first grid to use also a api store.

[walldorff]

Thank you Condor, for the work and effort put in this great extension. Wish you a successful 2011 !

Roland

[colinm]

Hello,
this extension is very nice .... easy to use .. i guess perfect ... but i got the following problem: when i press the next page in the pagingtoolbar, the next values appear correctly still, the Loading AlertBox doesn't disappear and freeze the screen.

Here is my code, first I define a grid having a tolbar:

	    
OriginalGridTab = Ext.extend(Ext.grid.GridPanel, {
    bbar   : [], 
    initComponent: function(){
        Ext.apply(this, { });
        OriginalGridTab.superclass.initComponent.apply(this, arguments);
            var ptb= new Ext.ux.PagingToolbar({
		      pageSize: 10,
		      store: this.store,
		      displayInfo: true,
		      displayMsg: 'Assays displayed {0} - {1} of {2}',
		      emptyMsg: "No assays to display"
			  });
	    this.getBottomToolbar().add(ptb);
	}
});

and here i create it:

	var ds = new Ext.ux.data.PagingArrayStore({
             fields : keysamples, 
             data : datasamples , 
             lastOptions: {params: {start: 0, limit: 10}}
        });
	var origgrid = new OriginalGridTab({ store : ds, cm : cm, viewConfig: { forceFit:true },loadMask:true});

as i said, everything is working fine (and if i removed the paging stuff, it works perfectly ... but too slow so i need it) except when i press the next button.
the debugger gives me the following exception:

Uncaught TypeError: Cannot call method 'child' of undefined
setLink          Exporter-all.js:157
EXTUTIL.Event.fire        ext-all-debug.js:310
EXTUTIL.Observable.fireEvent         ext-all-debug.js:54
(anonymous function)        PagingStore.js:168
(anonymous function)ext-base.js:7

which refers to the line 168 in PagingStore which is the following:

  this.fireEvent("load", this, r, options);

Can anyone help me?
thx
colin

[Condor]

It says the error is on line: setLink Exporter-all.js:157

I have no idea what that code is.

[colinm]

thanks for the fast reply ...
indeed, someone tested the Exporter-all.js script (this provides functionality to export grid store to excel like format). Well apparently that script was not working so well and was no longer used ... .but still loaded ...
i removed it and everything works fine ...
thx again for your extension and happy new year

colin