LeviFiction wrote:There are several methods to achieve this depending on what you want.
[SNIPPED]
3) Finally there's Gary's pause script. This is different from simply waiting for interaction from the user or waiting for a period of time. Gary's pause script lets you run half of the code of your script then save any necessary information to the image description for later retrieval. When you run the script a second time it starts from where it left off. This is used by some script authors to let the person running the script choose settings for their tools, or perform specific edits in between sections of the script. I don't have an example of this. The script template for Gary's Pause Script and how to use it can be fond in the script references topic on this board.
For clarification, Gary Barton's Pause script doesn't necessarily only let you run half the script then the other half, but allows you to pause as many times as needed to perform user input, then continue to the next step by running it again, etc., until all steps of the script have been run.
That said, if an example of the Pause script is wanted, I posted a script that does only use two steps and, of course, uses Gary's script to achieve it. The only editing needed by anyone using the script is minor and, in my script (link below) can be see at lines 16 and 157 of the script (def DoStep1(Environment): and def DoStep2(Environment): respectively.) Any number of DoSteps can be created as needed, named in numerical order (that info is also in the header of Gary's script). My script, used as my example, can be found here:
http://forum.corel.com/EN/viewtopic.php?f=104&t=60059
Gary's Pause script is simply pasted after the last step in your recorded or written script, shown starting at line 273 of my script. Gary's Pause script is here (the download link for it is near the bottom of the page that this link goes to, after his explanation of the script):
http://pixelnook.vapho.com/PauseScriptDemo.htm