| Summary: | sort by album should prefer track number over artist | ||
|---|---|---|---|
| Product: | [Applications] juk | Reporter: | Braden MacDonald <mail> |
| Component: | general | Assignee: | Scott Wheeler <wheeler> |
| Status: | ASSIGNED --- | ||
| Severity: | wishlist | CC: | null |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandrake RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot of mis-sort | ||
|
Description
Braden MacDonald
2003-11-30 19:53:08 UTC
Created attachment 3479 [details]
Screenshot of mis-sort
You can see in this screenshot that the tracks on the album are not sorted by
track number, but rather by the artist's name.
Ok, this will take a little more logic because album names are not always unique. Think of i.e. "Greatest Hits" which would potentially match a number of "real" albums. But what I can probably do is to change it to where things are sorted by track number in the case that the album name is unique. How likely is the corner case of multiple albums with the same name going to occur? In such cases the artist will differ To me, solving bug #79509 would solve this bug as well; if I can influence the implicit sort order, I'd be more than happy. Right now it is the implicit sort order that is biting me: it sorts on Artist before Track. If either the default implicit sort order is changed, or the sort order is configurable, I'd be very happy. On the point of a configurable sort order... I agree this solves this problem and other problems too probably. I would like an easy to way to control the secondary sort order. For example, if I click on the tracknumber column followed by the the album column then 1st order sort order is by album, and within that tracknumber. If I click any other two columns in sequence I can create a new 2nd and 1st level sort order. So the second last column selected is the secondary sort order. You could extend this logic to 3 levels if you wanted. To me this is intuitive and makes this bug go away. |