Feat. Req: more options for output fldr in batch proccessing

[fbachofner]

I would like to be able to:

delete * from the output folder prior to starting a batch operation

This would make it easier to deal with all currently transformed images going to a "standardized" folder I use for such operations without needing to remember to clear the folder first . . . or (worse, when I forget) to selectively delete unwanted files from the output folder after transforming a bunch of files and realizing there were already unwanted files there.

Alternatively, perhaps a more powerful feature would allow calling a script either before or after the transformation (this would obviously allow far more options than described above).

This would be a great enhancement for XNView Classic, too.

[m.Th.]

delete * from the output folder prior to starting a batch operation

No, no! - just yesterday instead of converting some RAW files in C:\output\myTempFolderForNewProject I accidentally converted them in C:\Output

Having a checkbox enabled (by default or left checked from the previous session) which will blindly delete all the files from destination will be a disaster!

Alternatively, perhaps a more powerful feature would allow calling a script either before or after the transformation (this would obviously allow far more options than described above).

Yes, Yes! - run an optional command before and an optional command after the Batch Processing would be a very great addition. This will be also in the spirit of the last discussions.

As always in such cases, there is a problem to solve: parameters. Which parameters to be passed to command/script?

...Remember that we don't have only the output folder as a target for Batch Convert but also, ZIP, Picasa, Flickr etc. - should we pass as parameter the temporary folder in which the conversion is done?

[fbachofner]

No, no! - just yesterday instead of converting some RAW files in C:\output\myTempFolderForNewProject I accidentally converted them in C:\Output

Having a checkbox enabled (by default or left checked from the previous session) which will blindly delete all the files from destination will be a disaster!

Yet you enthusiastically support calling batch files which can do far greater damage (depending on what you script, of course)? Interesting!

The secret to avoiding most problems with such a "delete * from output folder" option would be to put it into an advanced mode tab (of course I would argue that batch processing is already basically "advanced mode" XNView!).

It could also DEFAULT to NOT be checked each time batch processing dialog is opened (unless enabled by a batch processing script.

[m.Th.]

No, no! - just yesterday instead of converting some RAW files in C:\output\myTempFolderForNewProject I accidentally converted them in C:\Output

Having a checkbox enabled (by default or left checked from the previous session) which will blindly delete all the files from destination will be a disaster!

Yet you enthusiastically support calling batch files which can do far greater damage (depending on what you script, of course)? Interesting!

Yes - "depending on your script". This is the key. Because in my script I can put "del *.* from c:\output\temp" which it will be safe if accidentally I change the output folder. Also, there are more and harder steps involved in building a batch file and assigning it to an event in the Batch Processing engine (either Before Process, either After Process). Hence is far harder to shoot yourself in the foot. And this is true especially for the beginners.

The secret to avoiding most problems with such a "delete * from output folder" option would be to put it into an advanced mode tab

An entire tab for a single checkbox? Hmmm... ...while all the other output settings are in the "Output" tab?.... ...mhmm.... I don't know that it is the best solution. Just IMHO of course.

(of course I would argue that batch processing is already basically "advanced mode" XNView!).

It could also DEFAULT to NOT be checked each time batch processing dialog is opened (unless enabled by a batch processing script.

Yes, but then you will forget to enable it when you want it. I still tend to prefer Before Process/After Process custom scripts selected from a drop-down edit list.