View Issue Details

IDProjectCategoryView StatusLast Update
0020818MMW 5Collectionspublic2024-04-19 17:01
Reporterbarrym Assigned To 
PriorityurgentSeverityminorReproducibilityalways
Status feedbackResolutionreopened 
PlatformWindowsOS-OS Version10
Product Version5.1 
Target Version5.1Fixed in Version5.1 
Summary0020818: Collection criteria is ignored when viewing the collection's Classification node
DescriptionCollection criteria is ignored when viewing the collection's Classification node
Steps To Reproduce1. 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 Informationhttps://www.mediamonkey.com/forum/viewtopic.php?t=106010
TagsNo tags attached.
Fixed in build3014

Activities

michal

2024-04-10 08:48

developer   ~0075060

Last edited: 2024-04-10 08:59

Fixed in build 3014. Filtering should work in these nodes now too.

lowlander

2024-04-12 15:12

developer   ~0075092

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.

michal

2024-04-12 15:18

developer   ~0075095

1) it is by design and the same as in MM4. It allows to move files to the node = assign that classification.

michal

2024-04-12 15:25

developer   ~0075096

2) I think it is correct behavior (similar to Rating nodes), but assigning to Rusty to decide.

rusty

2024-04-19 17:01

administrator   ~0075159

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.