2011
Table Of Contents
- Contents
- Basic Customization
- Overview of Customization
- Organize Program and Support Files
- Customize a Publish to Web Template
- Define Custom Commands
- Record and Modify Action Macros
- Custom Linetypes
- Custom Hatch Patterns
- User Interface Customization
- Understand User Interface Customization
- Work with the Customize User Interface (CUI) Editor
- Create and Manage Customization Files
- Customize Commands
- Overview of Commands
- Create, Edit, and Reuse Commands
- Create Macros
- Overview of Macros
- Use Special Control Characters in Macros
- Pause for User Input in Macros
- Provide International Support in Macros
- Use Built-in Commands in Macros
- Repeat Commands in Macros
- Use Single Object Selection Mode in Macros
- Use Macros to Swap User Interface Elements
- Use Conditional Expressions in Macros
- Use AutoLISP in Macros
- Control the Display of Command Items
- Assign Search Tags
- Create Tooltips and Extended Help for Commands
- Create Status Line Help Messages
- Assign, Create, and Manage Images for Commands
- Customize User Interface Elements
- Load an AutoLISP File
- Customize Workspaces
- Transfer and Migrate Customization
- Customize User Interface (CUI) Editor FAQs
- DIESEL
- Slides and Command Scripts
- Introduction to Programming Interfaces
- Shapes and Shape Fonts
- Overview of Shape Files
- Create Shape Definition Files
- Shape Descriptions
- Vector Length and Direction Code
- Special Codes
- Use Special Codes
- Codes 0, 1, and 2: End of Shape and Draw Mode Control
- Codes 3 and 4: Size Control
- Codes 5 and 6: Location Save/Restore
- Code 7: Subshape
- Codes 8 and 9: X-Y Displacements
- Code 00A: Octant Arc
- Code 00B: Fractional Arc
- Codes 00C and 00D: Bulge-Specified Arcs
- Code 00E: Flag Vertical Text Command
- Text Font Descriptions
- Sample Files
- Big Font Descriptions
- Unicode Font Descriptions
- Superscripts and Subscripts in SHX Files
- Index
Quick Reference
Commands
APPLOAD
Loads and unloads applications and defines which applications to load at
startup.
System Variables
ACADLSPASDOC
Controls whether the acad.lsp file is loaded into every drawing or just the
first drawing opened in a session.
The ACAD.LSP File
You can create an acad.lsp file if you regularly use specific AutoLISP routines.
When you start AutoCAD, it searches the support file search path for an acad.lsp
file. If an acad.lsp file is found, it is loaded into memory.
The acad.lsp file is loaded at each drawing session startup when AutoCAD is
launched. Because the acad.lsp file is intended to be used for application-specific
startup routines, all functions and variables defined in an acad.lsp file are only
available in the first drawing. You will probably want to move routines that
should be available in all documents from your acad.lsp file into the acaddoc.lsp
file.
The recommended functionality of acad.lsp and acaddoc.lsp can be overridden
with the ACADLSPASDOC system variable. If the ACADLSPASDOC system
variable is set to 0 (the default setting), the acad.lsp file is loaded just once:
upon application startup. If ACADLSPASDOC is set to 1, the acad.lsp file is
reloaded with each new drawing.
The acad.lsp file can contain AutoLISP code for one or more routines, or just
a series of load function calls. The latter method is preferable, because
modification is easier. If you save the following code as an acad.lsp file, the
files mysessionapp1.lsp, databasesynch.lsp, and drawingmanager.lsp are loaded
every time you start AutoCAD.
(load "mysessionapp1")
(load "databasesynch")
(load "drawingmanager")
442 | Chapter 7 Introduction to Programming Interfaces