View Issue Details

IDProjectCategoryView StatusLast Update
0005615MMW v4Properties/Auto-Toolspublic2021-03-24 20:03
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilityalways
Status feedbackResolutionopen 
Product Version3.1 
Target Version4.1 
Summary0005615: Changes to directory capitalization aren't saved
DescriptionWhen the user makes a change to the capitalization of a directory (e.g. via the tree>Location>Folder, via Properties>Path, or via auto-organize), the changes show up in MM but not in Explorer.

This causes a secondary problem, that Files to Edit > Unorganized Tracks always contains a bunch of tracks that cannot be organized as described at http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=39440 .
TagsNo tags attached.
Fixed in build

Relationships

related to 0001412 feedbackjiri MMW 5 Changed capitalization not recognized in some cases and is inconsistent with MMA 
related to 0005616 closedpetr MMW v4 Files to Edit > Unorganized tracks often includes tracks that have been organized 
related to 0017691 closedmichal MMW 5 Image lookup, and properties do not work in some specific cases and some tag fields are missing 

Activities

rusty

2009-05-15 15:16

administrator   ~0017884

Comment from Jiri: This was already discussed in the past and it isn't a trivial issue. Also, it isn't clear whether user's changes should always be propagated. E.g. if you change folder name 'Music' to 'music' in Track Properties for one track, I'm not sure whether whole DB (i.e. easily 100k tracks) should be updated based on this.

rusty

2009-07-23 21:55

administrator   ~0018590

Re. the fact that such a change can affect the paths of hundreds of other files, sure that's possible--and expected. i.e. if the user changes the directory 'Music' to 'music', then it should be changed.

As a safeguard, MM would show the warning dialog that appears when > 50 tracks are modified.

jiri

2009-11-02 17:13

administrator   ~0019490

I'd possibly agree in the case of renaming tree>Location>Folder. However, e.g. in case of Properties>Path, the situation is quite different. I can imagine quite easily that a user simply modifies this path and doesn't care much about capitalization (since Windows filesystems don't require this). It would be quite surprising that such a change in folder capitalization would be reflected in filesystem.

I suppose that it can be fixed by ignoring capitalization for Unorganized tracks.