I think the example you have also loads all rows and doesn't use "page
fetching" to load only the first page, waiting until they click next page to
actually retrieve additional rows. It seems the example gets all rows, so
the sorting is all local and works on all data, no additional fetching takes
place.
Also, I noted in your onRowSelection() callback, you use:
int rowIdx = set.iterator().next().getRowIndex();
String id = pagingScrollTable.getDataTable().getHTML(rowIdx,
0);
Message m = tableModel.getMessageById(Long.parseLong(id));
I wondered why you took your ArrayList and then created the HashMap based on
ID, and it seems use use this scheme to get the selected row object. But
couldn't you just use the paging scroll table's method to get the selected
object directly:
int rowIdx = set.iterator().next().getRowIndex();
Message m = pagingScrollTable.geRowValue(rowIdx);
Or is there some other reason for your retrieval method? Thanks again for
your code example. I'm still working through and have basic table
functionality working now myself.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/google-web-toolkit?hl=.
