[SWINGX-479] Add client properties for sorting/filtering Created: 21/Mar/07  Updated: 28/Jan/11  Resolved: 11/Jan/11

Status: Resolved
Project: swingx
Component/s: TreeTable
Affects Version/s: 0.9.0
Fix Version/s: 1.6.3

Type: Improvement Priority: Major
Reporter: Karl Schaefer Assignee: kleopatra
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Operating System: All
Platform: All

Issuezilla Id: 479


The JXTreeTable has known issues with sorting and filtering. As such the
methods, setSortable and setFilters are no-ops. This dissuades users from
attempting sorting and filtering solutions, since they are required to modify
the JXTreeTable source.

I suggest adding client properties that will enable the use of the inherited
sorting and filtering. I will be easier for users to work with the inherited
code and also (hopefully) make it easier for users to come up with solutions to
the current problems.

I'd recommend "enable-super-sorting" and "enable-super-filtering".

Comment by Karl Schaefer [ 17/Nov/07 ]

My bug and I'm closing as won't fix. We'll just wait on Mustang to reevaluate
tree table sorting.

Comment by uvoigt [ 11/Jan/11 ]

See thread

Comment by kleopatra [ 11/Jan/11 ]

decided against both clientProperty and some single method to turn on the sorting - both
are not safe enough, IMO. Instead, added protected methods to access respective super
methods. Thus subclasses have explicitly re-implement the respective no-ops implementations
in JXTreeTable. Hope that's repellent enough for any hobby adventurer

committed as of revision #3915, JXTreeTableUnitTest has a (fake! no real sorting) example
of how to override


Generated at Tue May 26 14:00:08 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.