Remove a track from a crate triggers sorting

[Jean Claveau]

I often sort my tracks by number of stars to evaluate/rate them.

If I give, for example 3 stars to a non-rated track and then remove another one from the crate, all the crate list will be sorted, as if I had clicked on the column name.

It's a bit confusing even if not blocking.

[David Chocholatý (davidchocholaty)]

I will try to take a look on it.

[David Chocholatý (davidchocholaty)]

The problem is a little bit more broader. It can be seen in crates, tracks and playlists too. Every time you choose the rating column for sorting (ascending or descending, doesn't matter), than do some changes on star rating and than after action as remove track, add track, switch window between crates and tracks for example, a table is sorted by selected column and order. In my opinion, I agree that user expected behaviour especially when removing the track is, that the table is being unchanged. With adding a track to crate, the track will be added at the end of the tracks table. Can more experienced mixxx developer confirm to me, that this change with disable sorting for the listed situations is required? Thank you in advance.

[Daniel Schürmann (daschuer)]

Thank you for confirming. It sounds like this bug required deeper investigation to solve it.
I suggest to use a debugger and set a breakpoint to the select() function and reproduce the error. One you hit the breakpoint investigate the backtrace to find out why that is triggered when a track is removed.

[Swiftb0y (swiftb0y)]

Mixxx now uses GitHub for bug tracking. This bug has been migrated to:
https://github.com/mixxxdj/mixxx/issues/7619