by gpswaney » Wed Jul 29, 2015 12:51 am
If I click on the Album node, I normally sort on the Summary field, and the tracks for each album are shown in order in the main window, but Update&Next gives the random selection described above (if using Art & Details). My understanding is that I can explicitly select secondary, tertiary, etc. columns to sort on by holding Ctrl and clicking other column headers. If I click <Summary header>, Ctrl-<Track # header>, the displayed track order is unchanged (still correct) and the random selection behavior is still there with Update&Next.
If I select one album to view in the main window and then sort on Track Number, the Update&Next selection order seems to behave properly.
To avoid user confusion, I think Update&Next needs to proceed to whatever the next track currently displayed in the main window listing is, regardless of how the sort is specified to arrive at that listing. For example, if I request to sort on Summary (which is identical for every track on the same album, so the sort is ambiguous), Mediamonkey nicely decided on it's own to display the tracks in order. It makes no sense for Update&Next to resolve this ambiguity differently, i.e. they should never disagree.
However, it's certainly possible that I don't really understand how to operate the multi-column sort feature, but that doesn't change my argument above.
If I click on the Album node, I normally sort on the Summary field, and the tracks for each album are shown in order in the main window, but Update&Next gives the random selection described above (if using Art & Details). My understanding is that I can explicitly select secondary, tertiary, etc. columns to sort on by holding Ctrl and clicking other column headers. If I click <Summary header>, Ctrl-<Track # header>, the displayed track order is unchanged (still correct) and the random selection behavior is still there with Update&Next.
If I select one album to view in the main window and then sort on Track Number, the Update&Next selection order seems to behave properly.
To avoid user confusion, I think Update&Next needs to proceed to whatever the next track currently displayed in the main window listing is, regardless of how the sort is specified to arrive at that listing. For example, if I request to sort on Summary (which is identical for every track on the same album, so the sort is ambiguous), Mediamonkey nicely decided on it's own to display the tracks in order. It makes no sense for Update&Next to resolve this ambiguity differently, i.e. they should never disagree.
However, it's certainly possible that I don't really understand how to operate the multi-column sort feature, but that doesn't change my argument above.