[
https://issues.apache.org/jira/browse/PIVOT-300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Greg Brown resolved PIVOT-300.
------------------------------
Resolution: Fixed
The TableView sort API has been revised to be more flexible and provide better
support such that the caller is not responsible for implementing quite as much.
TableView now provides a "sort dictionary", a sorted set of key value pairs
where the keys are column names and the values are sort directions. Insertion
order is preserved.
TableView also now fires events associated with the sort dictionary, so a
caller can listen for sort events to determine when data needs to be re-sorted
rather than header press events. TableViewHeader now takes care of updating the
table view's sort state in response to header presses so a caller is no longer
responsible for handling this at the application level.
> Refine TableView sort API
> -------------------------
>
> Key: PIVOT-300
> URL: https://issues.apache.org/jira/browse/PIVOT-300
> Project: Pivot
> Issue Type: Improvement
> Components: wtk
> Reporter: Greg Brown
> Assignee: Greg Brown
> Fix For: 1.3.1
>
>
> The current API for managing sorting in TableView is cumbersome and
> inflexible. In particular, it doesn't convey any concept of sort order - only
> sort direction for individual columns. Managing sort order and sort state is
> left entirely to the caller - the platform should provide better support for
> this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
