@Anonymous
you would use a script to do that, as lisp cannot "continue" once the drawing that ran it closes.
Scripts are just text files with .scr extension that have acad commands typed in them.
Note that a space is an enter, but for commands that ask for a name, they accept spaces so you do a carriage return (new line).
You can load a script and lisp by dragging from explorer to the black drawing area of acad.
Scripts run instantly, not like lisps where you have to type the function name.
I even make lisps that make scripts and run them. That allows you to say, save current drawing, close, and open the next one alphabetically.
It takes a lot of testing though, and you should notice that in the VLIDE, you can double click before a paren, it will select to the end of the statement. Then right click and pick Inspect. It will show the results of the statement.
So classic debugging goes like this in the vlide:
1) put cursor at beginning of a statement you want to "stop" on. Hit F9 to see a red box there.
2) pick Tools->Load text in editor
3) run the function SSA or whatever on command line. It will run the lisp and stop at the break point.
4) select any variable and right click, Inspect to see the value at that moment
5) hit F8 to step forward, or shift F8 to do a whole statement at a time. Try it to see how it works.
6) at any time, select a statement and Inspect to see what it would give. You can actually edit your code and reinspect, but that also glitches the rest of the debug, it will kick you out.
7) keep hitting shift F8 to run through rest of code, or the little green arrow on debug toolbar.
8) red arrow on debug toolbar stops the debug at any time.
Learning to use that will make you 100x more powerful as then you can try stuff at runtime to get your code working.
Also, you can see where a routine glitches if it does. The debug will leave the cursor where it failed.
Read up on the use of the VLIDE. You can set up projects that compile to vlx, and use those projects to find things when you do larger programs.
internal protected virtual unsafe Human() : mostlyHarmless
I'm just here for the Shelties