Anstellos1 wrote: xbytor2 > thats the exact problem I'm having. If there is a "wrong" file into my batch, photoshop stop/ crash, is waiting for an action on my side... the whole idea of using photoshop droplets is to do it without me. Should I parse the files (I have jpegs; png and raws... parsing raws ?)? Would it be better like someone said to use a script that "try catch"? (no idea what it is or how to write this). I also red that photoshop image processing is skipping bad files, is that true ? how could I apply this technique ? bad file > skip > no crash > process continue running would be even better than the original validation idea |
"Unfortunately, there are types of jpeg corruptions that cause PS to throw up a 'Broke File' dialog in spite of how you open the file or have your DialogModes preferences set. PS just stops cold waiting for user interaction. I'll see if I can locate one of these that I used to test with. The last time I looked at this problem in depth (CS2 or CS3) PS was still misbehaving.
xbytor2 if much more of an expert than I am in the script area so will have to defer to him"
I would have to defer to xbytor2 since he is much more of an expert than I in scripting. If the Try....Catch construct does not work, than Image Processor in PS and also accessed by Bridge would fail under the same circumstances since that is the construct that script uses. Interesting
"How would you write that ? Are you saying that if I use this script at the beginning of my photoshop droplets, it won't crash on a bad file and continue looping on the next ?:"
If you want to use the Try...Catch constructs looking at the Image Processor Code from ExtendScript ToolKit (or other script editor) would let you see how it operates. They use the Try...Catch construct in multiple locations in that script.
At the highest level in Image Processor here is the basic code below for the Try...Catch construct with most everything else stripped out.
There are two main steps. One is to set the app.displayDialogs mode to NO. The second is to use the try...catch construct below. The error routine is the catch portion of the code just displays the error code. Then the dialog mode is reinstated to the original settings set by the User. The same construct is used deeper into the code so that would be a source of at least the approach Image Processor uses.
try {
// remember the dialog modes
gSaveDialogMode = app.displayDialogs;
app.displayDialogs = DialogModes.NO;
Code you want to execute goes here
}
// Lot's of things can go wrong
// Give a generic alert and see if they want the details
catch( e ) {
if ( e.number != 8007 ) { // don't report error on user cancel
alert( e + " : " + e.line );
}
}
// restore the dialog modes
app.displayDialogs = gSaveDialogMode;
9
Replies
AdChoices