A separate execution context is established for each document opened in AutoCAD, to allow the command processors and Visual LISP environments for each document to execute independently of each other. Each execution context maintains its own stack. All execution contexts work on common heap and static data. Execution contexts can only be switched when the system polls for more interactive input.
- Customization and Administration Guides
- DXF Reference
- AutoLISP and DCL
- ActiveX and VBA
- ObjectARX and Managed .NET
- ObjectARX: Developer's Guide
- ObjectARX Introductory Concepts
- Basic Interaction with AutoCAD
- Custom Objects
- Advanced Topics
- Table Linking
- Notification
- The Multiple Document Interface
- MDI Overview
- MDI Terminology
- SDI System Variable
- Levels of Compatibility
- Interacting with Multiple Documents
- Document Event Notification
- Application-Specific Document Objects
- Nonreentrant Commands
- Multi-Document Commands
- Disabling Document Switching
- Application Execution Context
- Database Undo and Transaction Management Facilities
- Document-Independent Databases
- An MDI-Aware Example Application
- Transaction Management
- Deep Cloning
- Protocol Extension
- Behavior Overrules
- Dynamic Blocks, Protocol Reactors, and Evaluation Graphs
- Input Point Processing
- Application Configuration
- Associative Framework
- ObjectARX Graphics, Geometry, and Boundary Representation Libraries
- Using COM for ObjectARX Development
- ObjectARX: Reference Guide
- ObjectARX: Managed .NET Developer's Guide
- ObjectARX: Managed .NET Reference Guide
- ObjectARX: Interoperability Guide
- ObjectARX: Migration Guide
- ObjectARX: Release Notes
- ObjectARX: Developer's Guide
- JavaScript
- AutoCAD Core Console