Hi.
We are using smartGWTPro version 2.5 and IE9.
We are using a ListGrid bound to a DataSource to display a user directory (paged data source on the server). The user directory can be sorted on first name or last name.
When the sort order is changed, we are calling
grid.setSort();
grid.invalidateCache();
In one of our cases, the client grid does not refresh correctly until all of the data is fetched from the server.
Example:
========
We have have 146 entries in the user directory on the server, and set the grid with a page size of 50.
When we select sort by last name on the client menu, we call the setSort() and invalidateCache() on the grid. We see the call to the server to fetch the first 50 names sorted by last name. The data returned by the server is sorted by last name. The grid shows loading data, but the data is not in the correct order when it refreshes. As we scroll down the grid, we see the client issue another fetch to get the next 50 items. The grid still doesn't show the data in the right order. As we scroll further down, it does the fetch to get the last page. Then the grid updates and shows the data correctly sorted by last name.
The interesting part is that when we switch the sort to 'first name', the grid behavior is the same for the server calls, BUT the client grid refreshes correctly on each call to the server. So the problem is only occurring when we try and sort on last name.
We are using smartGWTPro version 2.5 and IE9.
We are using a ListGrid bound to a DataSource to display a user directory (paged data source on the server). The user directory can be sorted on first name or last name.
When the sort order is changed, we are calling
grid.setSort();
grid.invalidateCache();
In one of our cases, the client grid does not refresh correctly until all of the data is fetched from the server.
Example:
========
We have have 146 entries in the user directory on the server, and set the grid with a page size of 50.
When we select sort by last name on the client menu, we call the setSort() and invalidateCache() on the grid. We see the call to the server to fetch the first 50 names sorted by last name. The data returned by the server is sorted by last name. The grid shows loading data, but the data is not in the correct order when it refreshes. As we scroll down the grid, we see the client issue another fetch to get the next 50 items. The grid still doesn't show the data in the right order. As we scroll further down, it does the fetch to get the last page. Then the grid updates and shows the data correctly sorted by last name.
The interesting part is that when we switch the sort to 'first name', the grid behavior is the same for the server calls, BUT the client grid refreshes correctly on each call to the server. So the problem is only occurring when we try and sort on last name.
Comment