first page start
though). The solution is to ensure, that the sort order is updated only and
only AFTER the data model is created and assigned to grid.model property.
--
View this message in context:
http://tapestry.1045711.n5.nabble.com/T5-Grid-default-sort-column-tp2425513p5042617.html
Sent from
Hi Szemere,
you are right, I also thought about this. But the result is a bit
confusing:
1. the nice little arrows don't show which column is sorted initially
(because Grid doesn't know about the sort order)
2. if the user figures out that the Grid is sorted by, say, the "Code"
column, an
n my menu), I get a
> NullPointerException at org.apache.tapestry5.corelib.components.Grid
> $DefaultGridSortModel.getSortConstraints(Grid.java:372). Somehow the
> dataModel seems to be null in this second request.
>
--
View this message in context:
http://www.nabble.co
I've got to say, I prefer the low-tech way of just sorting the collection
before I give it to the Tapestry grid - it's a lot simpler than the above.
This doesn't explain why you have the above issue, but it does give you a
workaround.
Szemere
Hi,
I have got a problem with setting the default sort column for a grid
after updating from 5.0.14 to 5.0.15.
This code, inspired by some comments on this list, works perfectly
nice on 5.0.14, but breaks on 5.0.15:
@SetupRender
public void setDefaultSortOrder()
{
if (grid.getSortModel(
