View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0020818 | MMW 5 | Collections | public | 2024-04-07 05:57 | 2024-05-23 22:46 |
Reporter | barrym | Assigned To | |||
Priority | urgent | Severity | minor | Reproducibility | always |
Status | closed | Resolution | reopened | ||
Platform | Windows | OS | - | OS Version | 10 |
Product Version | 5.1 | ||||
Target Version | 5.1 | Fixed in Version | 5.1 | ||
Summary | 0020818: Collection criteria is ignored when viewing the collection's Classification node | ||||
Description | Collection criteria is ignored when viewing the collection's Classification node | ||||
Steps To Reproduce | 1. Set a classification tag for a track, eg. Mood = Late 2. Open a node whose criteria excludes the track on some factor other than Classification settings 3. Open the Classification node within that Collection 4. ==> the mood=Late track is displayed, even though it should be excluded by the Collections Criteria | ||||
Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?t=106010 | ||||
Tags | No tags attached. | ||||
Fixed in build | 3014 | ||||
|
Fixed in build 3014. Filtering should work in these nodes now too. |
|
Verified on 3014. 1) The Classification nodes in the Media Tree show all values in Library, instead of only those with matching files in Collection (like Genre). 2) Classification sub-nodes (ex. Mood) shows sub-nodes with the option to Show all subnodes disabled. |
|
1) it is by design and the same as in MM4. It allows to move files to the node = assign that classification. |
|
2) I think it is correct behavior (similar to Rating nodes), but assigning to Rusty to decide. |
|
2) I see both points of view; on one hand, the argument for facilitating d&d between nodes can be made for other nodes (e.g. Artists, Genres) that don't currently enable subnodes, and on the other, one could argue that Rating, and Years which currently also have subnodes enabled, should not have them enabled for the same reason as Classifications. In any case, this should be moved to a separate bug for future consideration. 1) Again, both points of view are valid. If one considers that many classification and ratings nodes are (and should be) pre-populated, then MM should display all of the subnodes regardless of whether they're used. I suggest deferring this decision and moving these 2 issues 2 a new bug. |
|
Re-resolving based on 0020818:0075092 , and opened a new bug 0020922 to track the issues raised by Lowlander. |
|
Re verified 3022 rest will be handled in 0020922 |