View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001483 | MMW v4 | Properties/Auto-Tools | public | 2004-07-06 14:10 | 2009-09-12 00:15 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | tweak | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 3.1.1 | ||||
| Target Version | 3.1.1 | Fixed in Version | 3.1.2 | ||
| Summary | 0001483: Rating: allow user to reset to 'unknown' | ||||
| Description | Currently, the user can reset rating to unknown when editing in place in the tracklist, or via the properties dialog, however, if the user changes the rating via My Rating (System Tray, Context Menu) or via the categorization toolbar, then there's no way to reset the rating to 'Unknown'. Recommendation: add 'Unknown' as a possible entry when using these tools. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 1265 | ||||
|
|
I think that it's quite unlikely users will need to often change rating to 'Unknown' and thus I think it's better that this option isn't present everywhere. |
|
|
I find this option obsolete as it can be easily Archived thru scripting, there are already several scripts doing that. |
|
|
I disagree. I think that it makes more sense to change the rating to 'unknown' when the cursor is dragged all the way to the left, instead of showing a bomb. |
|
|
Jiri, if I'm right that could raise regression/complains from users in case that rating column is wider so that user can click on blank space in column for purpose to Select track and as I see in current design Ratings are aligned to left. |
|
|
Reminder sent to: jiri, peke, rusty I am little bit confused about this issue, what is the point here??? Peke's and Jiri's objections are opposites to the Rusty's. Isn't this issue just duplicate of 0003273 ?? |
|
|
I think we really could change it, so that instead of assigning the bomb to a track, rating would be set to Unknown. Then however, there wouldn't be an easy way how to assign the bomb to a track. That said, I wouldn't mind getting rid of the bomb completely, since it's quite nonstandard. |
|
|
I'll try to clarify: This bug was originally entered when ratings were configured via a drop-down menu, and when they didn't allow for rating to be set to 'unknown' via several portions of the UI. Both of these are no longer issues. However, whereas the Tracklist previously allowed the user to set ratings to 'unknown', since we've migrated to 'single-click-rating', it is no longer possible to set a rating of unknown (for both the tracklist and the player). In the tracklist: -Select a track -Move the cursor over the rating --> user can observe the change in the rating -Press and hold the mouse button when the cursor is to the left of the leftmost star -->the rating appears to change to unknown -Release the mouse button -->A 'bomb' appear! In the player -Select a track -Move the cursor over the rating --> user can observe the change in the rating -Press and hold/release the mouse button when the cursor is to the left of the leftmost star -->the rating changes to 1/2 star So to summarize the problems as they exist in 3.1.0.1256: 1) The behavior of one-click ratings differs between the Player and the Tracklist (Player can change to minimum of 1/2 star, Tracklist can change to Bomb) 2) In the tracklist, the 'leftmost' rating is 'Bomb' instead of 'unknown' even though unknown is more useful (due to the fact that 'bomb' is non-standard (in addition to the fact that the UI makes it look like rating is changing to 'unkwown' but then changes it to 'bomb'). The simple solution is to make ratings behave identically in both cases, so that placing the cursor in the leftmost position changes rating to 'unknown'. As far as Jiri's suggestion of eliminating support for 'bomb' from other portions of the UI, I think it's something we could do in the future, but I don't think we should do so right now. |
|
|
Ok, we should fix as suggested. |
|
|
Fixed in 1257 |
|
|
Verified 1257 |
|
|
Changed back to resolved as repeat test with 1259 not included this fix |
|
|
verified 1266 |
