columnview: multiselection vs sort
If a multiselection wraps a sort model, and the sorting changes, bad things happen to the selection state.
What really should happen is that the multiselection updates its off-to-the-side storage of the selection state to account for the changed positions of items.
But that is hard to do, since the sort list model does not provide the necessary information to track item positions across sort changes. It simply says "everything was removed and added"
Another alternative would be to make a sort model that also passes through selection information, and wrap models the other way around.
Edited by Andre Klapper