Customizing destination folder and file name - RealWorld forums

This is a great little App and does every thing I want - if only I could get the destination folder and filename to work!

I am trying to resize everything from one folder structure to another folder structure.

Here is my batch file:
PhotoResize800RHSM.exe F:\Test "-cF:\Test800\<PATH><NAME>.jpg"

I am trying to resize everything in the F:\Test folder and all it's subfolders to the F:\Test800 folder (and create the same subfolders)

I have copied your example exactly, but it always puts the files in the same folder as the source...

Help?

change it to: PhotoResize800RHSM.exe "-cF:\Test800\<PATH><NAME>.jpg" F:\Test

parameters are processed from left to right

thanks a lot - works like a dream!

I, sorry for reopening this thread, but I've just downloaded this useful program and I'm having similar problem.

I use a desktop shortcut and I've tried to set an output folder following your instruction and writing "C:\resized" in "From:", but that doesn't work.

Can you help me?

Thanks for your attention.

Great work, man! This thing is a real time-saver!

Took me a while to find out how exactly the -c option works, though: I thought that the <PATH> is simply ignored as it never appeared in my target folder system. Maybe it's worth pointing out the following:

When using the -r (recursive directory) option, the <PATH> is only THAT part of the images' filepath that you enter as source. (Maybe I also had a wrong idea what the <ROOT> is.) So, when you have a folder structure like

D:\
  MyImages
    England
    France
    Italy

and you use

PhotoResize.exe -w800 "-cM:\<PATH><NAME>.jpg" "D:\MyImages"

then your target file system structure will be

M:\
  England
  France
  Italy

Unless I'm wrong.

Yes, that is correct. <ROOT> is the entered path and <PATH> is relative path from ROOT to the currently processed file.

I use:

PhotoResize_1600RSQ90.exe "-cC:\MYFOLD\<PATH><NAME>.jpg" E:\MYFOLD

to resize images from my mobile HD. Program builds folder structure on drive C: such as on source well. But I hoped, the files not processed because of options (with short size less then 1600) will achieve a destination too. It is not. The program don't make a copy of file if there were no processing. I think it is wrong.