[REVIEW REQUEST] Improvements to TableView sorting
Knut Arne Vedaa
knut.arne.vedaa at broadpark.no
Tue Feb 19 14:41:34 PST 2013
John Hendrikx wrote:
> - Transforming a select range of 0-500000 to many smaller select ranges
> when a resort occurs
Can you actually get a range out of SelectionModel, and not just a
series of indices? It doesn't seem so from the API as far as I can tell.
> - Depending on the backing list, many random deletes in a huge List will
> be costly (ArrayList won't cut it, any Events being triggered on
> modification of the list will likely also introduce a huge bottleneck).
> Note that the use case specifically causes these deletes to be random!
> It's not possible to do it in a single remove event.
Can't you do it in a single operation if you use List#removeAll?
> - Resorting after every list change
It shouldn't be necessary for SortedList to re-sort after a delete, as
the order of the remaining items stays the same.
More information about the openjfx-dev