AutoLISP Command Calls vs ActiveX for Plotting Automation
Understand when to automate plotting through AutoCAD commands and when to use the Windows-only ActiveX object model.
Main idea: Command-based AutoLISP follows AutoCAD prompts; ActiveX works directly with Layout and Plot objects. The second is powerful but Windows-only.
Best use: Developers and advanced CAD users deciding how to build reusable plot tools.
Start with the manual workflow
Start by identifying whether the task is naturally a command sequence or a property change. Setting a Layout StyleSheet or CanonicalMediaName is direct in ActiveX; replaying -PUBLISH from a DSD can be simpler as a command.
Before automating a production workflow, review Autolisp Vs Scr Plot Automation, AutoLISP Plotting & PDF Automation, and CAD PDF & Publishing Guide.
Build the automation in small layers
Step 1 — Identify the platform
Where: Target workstation list
Do this: Decide whether the routine must support AutoCAD for Mac.
Check: If Mac support is required, avoid ActiveX-only design.
Step 2 — Identify the operation
Where: Manual workflow
Do this: Separate command-driven tasks from Layout/Plot property changes.
Check: The automation target is clear.
Step 3 — Prototype the smallest version
Where: One Layout
Do this: Use command/command-s or a small ActiveX call for one item.
Check: You can verify the effect immediately.
Step 4 — Add validation
Where: Before the change
Do this: Check Layout, plot mode, file or device conditions before writing properties.
Check: Bad inputs fail early.
Step 5 — Add batch logic last
Where: Multiple Layouts
Do this: Only loop after the single-item version is stable.
Check: The batch version is easier to debug.
How the same task looks in the two approaches
With command-based automation, your code behaves like a very fast operator at the command line: it starts -PLOT, answers prompts and waits for the command to finish. This can be portable and easy to compare with manual command history.
With ActiveX, your code works with objects and properties such as Layout.ConfigName, Layout.StyleSheet or Plot.PlotToFile. That avoids long prompt sequences and makes validation easier, but it ties the routine to the Windows ActiveX interface. A reference site should make that tradeoff explicit on every download.
What the code should control
- command and command-s
- vl-load-com
- vla-/vlax- functions
- Layout object properties
- Plot object PlotToFile/PlotToDevice
What you should deliberately leave manual at first
Avoid mixing several automation methods in the same first prototype. A routine that uses commands, ActiveX, external apps and file rewriting at once is difficult to verify.
Failure modes to design for
- ActiveX code is published as macOS-compatible.
- A command-driven routine depends on localized option text.
- A routine changes Layout properties without calling the needed refresh method.
- Plotting is started in the background when the ActiveX method requires foreground processing.
When this becomes a production tool
Document the platform boundary on every download page. For Windows-only downloads, say why they are Windows-only instead of letting Mac users discover it from an error.
Official Autodesk references
Frequently asked questions
Is ActiveX better than command-based AutoLISP?
Not automatically. ActiveX is excellent for object properties and Windows automation; command-based logic can be simpler and more portable.
Why does vl-load-com matter?
AutoCAD documents that ActiveX-related AutoLISP extensions should be loaded before vla/vlax code is used.
Can ActiveX plotting run on Mac?
No. Autodesk documents AutoLISP ActiveX support as Windows-only.
Explore more in AutoLISP Plotting & PDF Automation.