[
https://issues.apache.org/jira/browse/WICKET-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter Ertl resolved WICKET-2896.
--------------------------------
Resolution: Won't Fix
@Nicolas:
We (the wicket developers) did not want to change the current behavior of
unsorted -> ascending -> descending -> ascending -> descending -> ...
to
unsorted -> ascending -> descending -> unsorted -> ascending -> descending ->
...
since the users are accustomed to it and most GUI's (for example Windows
Explorer) behave the same.
However I added a the possibilty to @override
OrderByLink#nextSortOrder(SortOrder currentOrder)
and
OrderByBorder#newOrderByLink
so you should be able to customize the sorting behavior to your needs.
> OrderByLink should support a ASCENDING -> DESCENDING -> NONE cycle
> ------------------------------------------------------------------
>
> Key: WICKET-2896
> URL: https://issues.apache.org/jira/browse/WICKET-2896
> Project: Wicket
> Issue Type: Improvement
> Components: wicket-extensions
> Affects Versions: 1.4.8
> Reporter: nicolas de loof
> Assignee: Peter Ertl
> Priority: Trivial
> Fix For: 1.5-M4
>
>
> Trying to extend SortableDataProvider to support multiple sorting criteria
> (based on http://www.mail-archive.com/[email protected]/msg14246.html),
> the ordering feature on DataTable cannot be used to get back to the "NONE"
> state. A simple change in OrderByLink can be used to fix this :
> int newDir = ISortState.NONE;
> if ( oldDir == ISortState.NONE )
> {
> newDir = ISortState.ASCENDING;
> }
> if ( oldDir == ISortState.ASCENDING )
> {
> newDir = ISortState.DESCENDING;
> }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
