by Teknojnky » Fri Jan 16, 2009 4:03 pm
Neil Parks wrote:I believe that this is a design flaw. The program should assume that the content of the field is a directory, and should automatically insert the trailing backslash if the user fails to do so. And of course the program should offer to create the dir if it does not already exist.
If you use the button to open the destination dialog, you will get a properly formatted folder path that includes the trailing backslash.
I'll create a ticket, in that edit box should allow only folder paths, or provide the set destination wizard if it is intended to allow user specified file naming masks (like for auto-organize etc).
I agree with Chris, that it should NOT be assumed that content field is a directory since you can currently use auto-organize masks, and a valid example might be:
C:\Podcasts\<artist>-<title> (podcast)
If the option assumed that was a folder, then you would get separate folders for every podcast, instead of one podcast folder with artist-title files.
[quote="Neil Parks"]I believe that this is a design flaw. The program should assume that the content of the field is a directory, and should automatically insert the trailing backslash if the user fails to do so. And of course the program should offer to create the dir if it does not already exist.[/quote]
If you use the button to open the destination dialog, you will get a properly formatted folder path that includes the trailing backslash.
I'll create a ticket, in that edit box should allow only folder paths, or provide the set destination wizard if it is intended to allow user specified file naming masks (like for auto-organize etc).
I agree with Chris, that it should NOT be assumed that content field is a directory since you can currently use auto-organize masks, and a valid example might be:
C:\Podcasts\<artist>-<title> (podcast)
If the option assumed that was a folder, then you would get separate folders for every podcast, instead of one podcast folder with artist-title files.