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
A ComponentEntry element can have any of the following attributes attached
to it:
DescriptionAttribute
Optional for AutoLISP; Required for ObjectARX and
.NET - Component name; same as AppName in the
ObjectARX API AcadAppInfo class.
AppName
Component description; same as AppDescription in
the ObjectARX API AcadAppInfo class.
AppDescription
Component type; overrides the type derived from the
file extension provided in the ModuleName attribute.
AppType
The component type can be one of the following:
■ Arx – ObjectARX
■ Cui or CuiX– Partial customization
■ Mnu – Menu customization
■ Dbx – ObjectDBX
■ .Net – Managed or Mixed .NET assembly
■ Lisp or CompiledLisp – AutoLISP
■ Bundle – Bundle package
■ Dependency – Resource DLL (not to be loaded
into AutoCAD)
Relative path to component within the bundle; same
as ModuleName in the ObjectARX API AcadAppInfo
class.
ModuleName
The component type is determined from the file ex-
tension:
■ .arx – ObjectARX
■ .cuix – Partial customization
■ .dbx – ObjectDBX
■ .dll – Managed .NET assembly
■ .lsp, .fas, or .vlx – AutoLISP
It your application will handle multiple languages,
different versions of a specific component to support
different languages can be specified by combining
458 | Chapter 7 Introduction to Programming Interfaces