from http://bugs.musicbrainz.org/ticket/3652

In Options>FileNaming the Picard user can define a script for file renaming and - at the same time - creation of a folder structure (based on album title,etc.), but at present, Picard only executes the script correctly if "move files" is checked. Otherwise Picard truncates the script and applies only the part after the last slash, refusing to create the folder structure.

It is illogical to check '''"move files"''' in the case where the user does NOT want his/her files '''to move''' to a specific directory on the disk, but the folder structure to unfold at the '''same location'''. The only workaround is to choose "." as the target dir.

Moving files to a special directory is INDEPENDENT of creating a folder structure, so therefore, it is good that Picard offers both options independently ("rename files" section and "move files" section) but SINCE they are indeed independent, Picard should also treat them as such by obeing the user's scripting instructions, including the creation of subdirs.

Of course: Subdirs are created everytime you press save.

There are three solutions:

(1) Leave this behavious as is. After all, this is exactly consistent with what the user tells the program to do.

(2) Implementing BrianG's call for separate move and save buttons (Ticket #3449).

(3) "You just need to store the filepath when initially loadingthe file."(Fuchs, Ticket #1054). Fuchs provides a code example.

(4) "I agree that it's confusing, chrizoo. Perhaps the file naming format should be a separate textbox on the options to the "file subdirectory" format, whereby the latter is prepended in the code later only if you have "move files" enabled?" (voiceinsideyou, http://forums.musicbrainz.org/viewtopic.php?pid=3696#p3696)

Regardless of the implementation, the current possibility for the user to have a the folder structure unfold at the same location should not get lost in my view.