View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0008818 | MMW v4 | Playlist / Search | public | 2011-12-06 08:12 | 2012-01-23 22:37 |
| Reporter | Assigned To | ||||
| Priority | normal | Severity | text | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Platform | Windows | OS | 7 | OS Version | - |
| Product Version | 4.0.1 | ||||
| Target Version | 4.1 | ||||
| Summary | 0008818: Favorites not Heard Recently (1hr) and Top 50 is reverse | ||||
| Description | See the Advanced tag or list to confirm this. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This is working correctly for me. i.e. the 'Not heard recently' playlist shows content that hasn't been heard recently. However, there is an element of confusion that perhaps is what you're raising: Last Played: A..Z : means Oldest to Newest Last Played: Z..A : means Newest to Oldest I would have expected the opposite in both cases. |
|
|
I also cannot reproduce. As for the confusion, changing the 'A..Z' to 'Z..A' only for the 'Last Played' could be confusing and problematic as the others date/time values like 'Added' would behave inconsistently. I would suggest the following string changes: 'A..Z' -> 'Ascending' 'Z..A' -> 'Descending' |
|
|
I don't think that the suggested string changes improves things at all--the problem is that it's a little bit confusing to understand what A..Z or Ascending means in relation to how recently something has been heard. The only real solution would be to use different terminology depending on the field being sorted on. e.g. date: oldest..newest, #: Ascending..descending, Alphabetic order: A..Z, Z..A |
