2012
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
- 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
- Migrate and Transfer Custom Settings and Files
- Index
NOTE VBA and AutoLISP
®
scripts that run at startup should check for whether the
AutoCAD process is visible or invisible. If the process is invisible, the script should
not execute, because the process may be performing background plotting or
publishing operations. To check for whether the AutoCAD process is visible or
invisible, you can use the Visible property of the Application object in the AutoCAD
Object Model.
You could run a script at startup to open a drawing by using the following
syntax in the Run dialog box:
ACAD drawing_name /b setup
All file names that contain embedded spaces must be enclosed in double
quotes, for example, “guest house”.
You can also specify the view that is displayed when the drawing opens by
using the /v switch and the view name. The /b switch and the script file must
be the last parameter listed.
Including the file extensions .exe, .dwg, .dwt, and .scr is optional. If AutoCAD
cannot find the script file, AutoCAD reports that it cannot open the file.
To run the same script at startup but create a new drawing using the
MyTemplate.dwt file as the template, enter the following in the Run dialog box:
ACAD /t MyTemplate /b setup
This command creates a new drawing and issues a sequence of setup commands
from the setup.scr file. When the script has finished running, the command
prompt is displayed.
If you want to use the default template for the new drawing, you can omit
the /t switch and the template file name.
NOTE You can no longer use this method to start a new drawing and give it a
name. Name the drawing when you save it.
To run a script at startup
1 Click Start menu (Windows) ➤ Run.
2 In the Run dialog box, enter acad drawing_name
/b script_name.
To start a new file, instead of a drawing file name, enter the /t switch and
the name of a template file: /t template_drawing.
To open a drawing file to a particular view, follow the drawing name
with the /v switch and the name of the view: /v view_name.
Run Scripts at Startup | 419