TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: Marc'Antonio Alessi on November 15, 2016, 02:27:59 AM
-
I discovered out right now the new SCRIPTCALL command (A2016), someone has used it? There are some examples?
-
Haven't used it myself but from the help:
You can invoke a script at startup or run a script using either the SCRIPT or the SCRIPTCALL command. The difference is that the SCRIPTCALL command can execute nested scripts in addition to commands. With the SCRIPT command, if a script is currently active when the SCRIPT command is invoked, the script is stopped.
Basically allows one to nest or chain scripts (like the call command in batch files). I typically only use scripts generated by, and invoked from LISP. While I've never been tripped up by the lilimitation of SCRIPT, its sibling command may prove useful some day. Thanks for the heads up Marc.
-
Haven't used it myself but from the help:
You can invoke a script at startup or run a script using either the SCRIPT or the SCRIPTCALL command. The difference is that the SCRIPTCALL command can execute nested scripts in addition to commands. With the SCRIPT command, if a script is currently active when the SCRIPT command is invoked, the script is stopped.
Basically allows one to nest or chain scripts (like the call command in batch files). I typically only use scripts generated by, and invoked from LISP. While I've never been tripped up by the lilimitation of SCRIPT, its sibling command may prove useful some day. Thanks for the heads up Marc.
For me the best method was to use (vl-cmdf "_.VBASTMT" ...), as long as you could. The script is less controllable in the event of errors and once launched you can not perform other operations at its end, see:
https://www.theswamp.org/index.php?topic=43869.msg492002#msg492002