[SWINGX-1195] SortManager: remove last row produces incorrect selection Created: 22/Oct/09  Updated: 28/Jan/11  Resolved: 05/Nov/10

Status: Resolved
Project: swingx
Component/s: Sort/filter
Affects Version/s: 1.6
Fix Version/s: 1.6.3

Type: Bug Priority: Major
Reporter: kleopatra 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: 1,195


happens if

  • table/list unsorted but with RowSorter
  • last row selected
  • remove last row

most obvious if there are other rows selected above, and removing all selected starting
from first: then the last is not removed. If the last is the single selected, the lead/anchor
is reset to -1

reported in core forum:

same in swingx - as we rely on core. Sigh, and I had hoped to never again have to cope
with low-level sorting side-effects


Comment by kleopatra [ 04/Nov/10 ]

was fixed during last round of sorter cleanup
added/updated tests

Generated at Fri Oct 21 13:30:15 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.