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
Localized Web site can be specified by combining URL
with a locale code. See Supported Locale Codes on
page 461 for a full list of supported locale codes.
Developer or company contact email address for the
plug-in.
Email
An international contact email address can be specified
by combining Email with a locale code. See Supported
Locale Codes on page 461 for a full list of supported
locale codes.
Components Element
The Components element is used to specify the components that make up
one version of the plug-in.
More than one Components elements can be used to identify the components
for a plug-in; each Components element can identify one or more components.
Platform and product information for a Components element is defined by
the
RuntimeRequirements element on page 455.
For example, one Components element might define the 32-bit version of the
plug-in, while another might define the 64-bit Windows or Mac OSX version.
Along with the RuntimeRequirements element, the Components element
might contain one or more ComponentEntry elements. The ComponentEntry
element
on page 457 is used to define the individual files that need to be loaded
by AutoCAD when the plug-in is ran.
RuntimeRequirements Element
The RuntimeRequirements element is recommended and is used to control
which operating systems, platforms, releases, and languages the components
can be used with.
It is also used to define AutoCAD support paths that are required for
components in that Components section. You can specify as may sets of
components as needed. If not included, it is assumed that all components are
compatible with all AutoCAD and AutoCAD-based products, releases, and
operating systems.
PackageContents.xml Format | 455