View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001769 | MMW v4 | Properties/Auto-Tools | public | 2005-01-28 19:11 | 2005-01-31 23:11 |
| Reporter | rusty | Assigned To | |||
| Priority | immediate | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Fixed in Version | 2.3 | ||||
| Summary | 0001769: Auto-Tag from Amazon: tracks with '?' shouldn't be selected | ||||
| Description | As pointed out by sadao at http://www.mediamonkey.com/forum/viewtopic.php?t=3276 , if auto-tag from Amazon cannot find a matching track # (i.e. a '?' appears), then it would make sense to not automatically check off the associated checkbox. If this is simple to implement, then let's include, otherwize we can push to 2.4. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 836 | ||||
|
|
I don't agree with this, if user selects a set of tracks then they will usually belong to an album. Then, even if some tracks aren't automatically matched, user will usually want to modify album title, etc. for all the tracks. Anyway, even if you or someone else doesn't agree with the above, the suggested fix would have very problematic logic - if a track is automatically unchecked, what if user changes selected album, should it be checked again? (And similar problems...) |
|
|
The problem is that users often use 'Auto-tag from Amazon' _without_ knowing which tracks are part of an Album. e.g. select five tracks by U2 and run Auto-Tag from Amazon. In this case, (or in any case where the contents of the Amazon DB are correct), it is preferable to _not_ select items with a '?'. If you feel that there's a usability problem with the above, it can be easily rectified by havinga single 'check all' checkbox at the top, to check/uncheck these items. As far as the problem with the logic, I'm not sure I understand. I see the logic as: anytime a search is initiated --> items returned with a '?' are unchecked (only those with a match should be checked). |
|
|
As discussed over IM, fixed in build 836 the way described here, at least for now. |
|
|
Verified 836. |
