estockly
(Ed Stockly)
April 4, 2017, 10:54pm
#1
I’m not sure this is a bug, and but this behavior is not familiar to me.
I opened applet that I’ve been using for years. It’s a stay-open applet with an idle handler and a quit handler.
When it’s finished its work it has “tell me to quit” command.
It also has an:
on quit
continue quit
end quit
This works just fine as an applet. It runs until it’s done then it stops running.
In Script Debugger, the script seems to ignore the “continue quit” command in the quit handler.
As a result, after the tell me to quit command, the script keeps running in SD.
Is this a new behavior for continue quit in SD?
The quit command tells an applet to quit – the script’s going no further is just a byproduct of that.
Think of a script as a bunch of handlers. As long as they exist, they can be called.
alldritt
(Mark Alldritt)
April 5, 2017, 12:26am
#3
Just to add to Shane’s explanation, Script Debugger explicitly disallows a script to quit
its self as that would mean causing the host application (Script Debugger) to quit.
estockly
(Ed Stockly)
April 5, 2017, 4:45pm
#4
OK, thanks, it’s been a while since I’ve edited this script and I think I expected the script’s execution to stop on the continue quit command.
At runtime, if x is true, then the “do more stuff” part would never run, but it does in SD.
if x then tell me to quit
–do more stuff