Batch done script using scpt file
Hey folks,
I tried to
and saved in background scripts folder, but nothing worked.
I tried also to
Did anyone get to use this function successfully here?
Help much appreciated Capture One Master 😄
I tried to
set batch done script to (display dialog "Done")and saved in background scripts folder, but nothing worked.
I tried also to
set newDoc to make new document with properties {name:sessionName, path:sessionPath, batch done script: (display dialog "Done")}Did anyone get to use this function successfully here?
Help much appreciated Capture One Master 😄
0
-
Again I was impatient! by giving up too soon, and asking, couldn't go to sleep without figuring out what was wrong.
batch done script is not a document property "Duhh" 😂
and in the dictionary, it asks for either text or file.
I created a separate script and pointed it out to it,
so it looks like :
set batch done script to alias "Macintosh HD:Users:USER:runme.scpt"
Placed in in the Background scripts folder. processed couple of images .. and BAM!! 💡 worked!
now I can go to bed.
Hope this will save someone the struggle in the future.0 -
I started testing things after your first post and didn't get to reply because of work, but now that I had applied a processing done script (similar to batch done) it keeps running whatever script that is that I attached...but i can't for the life of me figure out what the original script was or how to stop it!
Any idea where that data is saved once it has been attached? I removed all folder actions, scripts from the Capture One scripts folder, etc. It still auto-plays. Ugh.0 -
Sorry for the quick reply with an answer to my own question. Apparently Capture One saves the path for batch done, processing done, capture done scripts in its main preferences file. I assumed it was only going to use the done script when I ran the parent script that had originally assigned it. I guess that's not the case.
To clear it, I just created a new AppleScript:
tell application "Capture One 10"
set batch done script to ""
set processing done script to ""
set capture done script to ""
end tell
This effectively clears the script out for each of those three follow-up scripts.0 -
I did not experience this issue, maybe because I cleared the external scripts folder.
But what I ended up doing for this job was to define the "batch / Process done scripts" in the initial create session scripts so it changes with the nature of the session type the user chooses.
I would totally use the snippet you provided, as a cleanup block in a global reset script.0
Post ist für Kommentare geschlossen.
Kommentare
4 Kommentare