Opened 12 years ago

Closed 11 years ago

#5261 closed defect (fixed)

dojox grid: when model.requestRows() is called, grid sort state is lost

Reported by: guest Owned by: sorvell
Priority: high Milestone: 1.2
Component: DojoX Grid Version: 1.0
Keywords: grid sort Cc:
Blocked By: Blocking:

Description

I set up a store, a model, a view, a layout like so (some pieces deleted for brevity):

this.devStore = new dojox.data.QueryReadStore?({

jsId: 'devStore', doClientPaging: false, url : url

}); this.layout = [this.view]; this.model = new dojox.grid.data.DojoData?(null, this.devStore, {

jsId: 'model', rowsPerPage: 3000, clientSort: true, query: {

d_hostid: '*'

}

});

Then, when I do this, to update the data from the server:

this.model.requestRows(0,3000);

the sorting of the grid is reset to "default" rather than retaining the sorting order in place when the requestRows() was called.

Selection, and scrolling are retained, but not sorting.

jong@… if more information is required

Change History (4)

comment:1 Changed 12 years ago by guest

Interestingly, when the actual xhr call is in process for that requestRows(), the grid briefly resorts to the sort state it should be showing, but when the requestRows() call is finished, it changes to a default sorting.

So for brief periods when the xhr call is in flight, the sorting is correct.

jong@…

comment:2 Changed 11 years ago by haysmark

I also notice this with the DojoData? model. It doesn't seem to happen with Table.

Additionally, the reverse sort seems to pick random page points as the "start" of the data. When I scroll down to the bottom of a reverse sort, there are just empty cells.

comment:3 Changed 11 years ago by dylan

Milestone: 1.2

comment:4 Changed 11 years ago by wolfram

Resolution: fixed
Status: newclosed

Please check again, I tested it and I think it was fixed with [13168]

Note: See TracTickets for help on using tickets.