Patrick Hughes, owner of Engineered Design Solutions and builder of CadTempo continues his BricsCAD performance story here. In this installment, Patrick dives deep into the scripting engine built into CadTempo…
A Tale of… Whoa! (Part II)
by Patrick Hughes
Here’s how CadTempo’s script maker works:
Create a script template
“Load…” will fill the text memo box with a selected script template (*.scr-tmp). “Save…” will save the current text memo box contents to a script template. Here are the full contents for this script template:
_purge a * n
_purge a * n
The “Filename” is a place holder for the drawings that will be opened and operated on. There are times when a batch process will not complete due to unforeseen problem drawings, so the next line loads a small lisp file and logs the drawing name. Zoom all, then two purge sequences. Load the ColorUpd.lsp file,which automatically executes. Qsave the drawing, then close.
Create the batch script
Check all drawings to be processed…
When you click “Create” you are shown a list of selected drawings:
Selecting “OK” will prompt for a batch script name, and save the script. This one looks like:
Run the batch script
I was now ready to conduct my comparison test so I fired up AutoCAD with a blank drawing. I prefer to start a batch script this way rather than to start with command line switches. I also wanted to use CadTempo to record the elapsed time so I prepared to begin a new task with the built in Task Timer.
After issuing the SCRIPT command in AutoCAD, I navigated to where I had saved the batch script, I started the Task Timer, then initiated the script.
In part three of this three-part post, Patrick will share the amazing results of his BricsCAD performance testing.