I’m not totally sure, but I suspect what you have in mind is not practicable.
Why not just split the Script in two?
It should certainly be possible to insert a confirm-dialog in a Script and have the Script continue only on confirm and stop on cancel.
The Scripts could store the information that the Script has been cancelled in a txt-file and have it elaluate the txt-file and only run a certain part depending on that, but it seems cumbersome.
What exactly is this about?
There are a few ways that this can be done:
The script could write the code to the open document or a file and when run again the script would check to see if the code exists.
Another way is to use a set of scripts one to open and do the first part and a second script to do the rest of the code.
For an example see ...
Thanks Paul and c.pfaffenbichler. The hardest part for me is understanding how to keep persistence and variable state from a script that is halted, and carry that information over to an entirely different script that resumes execution. Just briefly looking over the scripts in the link that Paul posted, I believe it's done with XML ... correct?
No there is no XML, it uses app.putCustomOptions(), app.getCustomOptions() to store and retrieve the required data, another example is here...
Great, Paul ... thanks for pointing me in the right direction. I was hoping something like this existed in ES to handle persistence.
Thanks again, I really appreciate it!