Renaming classes for each new version is the simplest method of avoiding versioning conflicts, as it does not involve implementing new data elements or functions to detect and respond to different class version numbers. However, the logistics of dealing with new and old class names can be complicated.
- 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
- Proxy Objects
- Object Enablers
- Deriving a Custom ObjectARX Class
- Deriving from AcDbObject
- Overriding AcDbObject Virtual Functions
- Implementing Member Functions
- Filing Objects to DWG and DXF Files
- Object References
- Ownership References
- Pointer References
- Long Transaction Issues for Custom Objects
- Purge
- Undo and Redo
- subErase, subOpen, subClose, and subCancel
- Example of a Custom Object Class
- Object Version Support
- Deriving from AcDbEntity
- Advanced Topics
- 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