View Issue Details

IDProjectCategoryView StatusLast Update
0017843MediaMonkey 5Main Panel: Toolbars & Menuspublic2021-07-27 22:15
Reporterpeke Assigned To 
Status feedbackResolutionopen 
Product Version5.0 
Target Version5.0.2 
Summary0017843: Clasifications: Unlike Genre Classifications are not Auto cleaned on Refresh
DescriptionUnlike Genre Classification are not Auto cleaned on Refresh

1. Edit single track properties
2. Under classification Tab in all classification categories tag Track with "!123"
3. Tag File
4. Open Tree [Collection] -> Classification Tempo -> !123
5. Select all tracks (1 in my test case) -> Properties -> Classification
6. Delete Temp to be Empty -> OK
7. Confirm That Main screen do not show track anymore
8. Select other tree node
9. Collapse tempo tree node
10. Expand Tempo Tree node and !123 is still available even it is empty
11. You can also select it in track properties.

Note: This also applies to other Classifications, where Artist, Genre, ... auto remove them from tree when there is no tracks.
Additional Information
TagsNo tags attached.
Fixed in build


related to 0018175 closedLudek Can't delete Classifications in Media Tree 



2021-05-09 23:25

administrator   ~0063110

Please correct me if I'm wrong, but afaik, Genres are pre-populated (and presumably not deleted) based on Genres that are included in the ID3V1 spec.

Similarly, it would probably be unexpected if MM deleted the default classifications that are included.


2021-05-10 09:40

developer   ~0063113

I see that it has always worked the same way in MM4 too. Peke probably means that newly created and subsequently deleted classification values shouldn't be available in the media tree, but this also works the same way in MM4 (empty tempo subnodes available).

So assigning to Rusty to decide what's is expected here and whether something needs to be changed for future versions.


2021-05-10 16:58

administrator   ~0063124

Last edited: 2021-05-10 16:59

View 2 revisions

I think that in general, a node should be deleted if it doesn't contain any content. The only exceptions to this might be if the node is pre-populated in MM (like ID3v1 genres, or classifications that are pre-populated).

BUT, even in the case of those exceptions, it would make sense to hide the nodes / entries in combo-lists if there are no such instances and the user has manually deleted the node.