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
DescriptionAttribute
NOTE For AutoCAD startup performance
reasons, it is very important to use this op-
tion when your components define com-
mands.
■ LoadOnAutoCADStartup - (Only applies to
ObjectARX and .NET modules.). Load when
AutoCAD starts up. When specified, this parameter
has precedence over all other parameters. It is re-
commended only to use LoadOnAutoCADStartup
when none of the other parameters are suitable,
disable it (set it to False) whenever possible. If the
LoadOnAutoCADStartup parameter is omitted,
then it defaults to enabled (set to True) unless
LoadOnCommandInvocation is enabled, in which
case LoadOnAutoCADStartup defaults to False.
■ LoadOnProxyDetection. Load when a proxy for
a custom entity is detected. By default, this para-
meter is enabled unless explicitly disabled (set to
False). When enabled (set to True), LoadOnAuto-
CADStartup should be disabled. Only applies to
ObjectDBX files.
■ LoadOnAppearance. Load when the product
detects the application bundle in one of the Ap-
plicationPlugins folders, thereby supporting in-
stant load on installation with no need to restart
AutoCAD. The parameter behaves the same way
as LoadOnAutoCADStartup except the load con-
text is relevant to when an application is installed
while the product is running, for instance if in-
stalled via the Apps tab on Autodesk Exchange.
Commands and Command Element
The Commands element is optional unless the LoadOnCommandInvocation
parameter is enabled for the LoadReasons attribute. Used to specify which
commands to register for LoadOnCommandInvocation.
You can specify more than one Command element as needed.
460 | Chapter 7 Introduction to Programming Interfaces