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
Codes on page 461 for a full list of supported locale
codes.
Icon for the plug-in; used in the installer and the Apps
tab on Autodesk Exchange. The icon should be 32x32
Icon
pixels in size and support 32-bit (Truecolor) color
depth. Recommend using a BMP or ICO file format.
NOTE All path specifiers are '/' and not '\', and paths
are relative to the root .bundle folder.
Help file that explains how to use the plug-in and
provides additional information about the plug-in.
Helpfile
It is recommended to place a How To section that
explains how to use the plug-in. The file can be an
ASCII text file, an HTML document, or PDF that con-
tains all the full documentation for the plug-in or
contains a set of redirects to where the content might
be located online.
Localized help files can be specified by combining
Helpfile with a locale code. See Supported Locale
Codes on page 461 for a full list of supported locale
codes.
NOTE All path specifiers are '/' and not '\', and paths
are relative to the root .bundle folder.
Unique GUID for the plug-in. A GUID must be gener-
ated for each unique plug-in, and is used for first run
ProductCode
notifications and as the installer ID for Add/Remove
Programs in Windows when installed from the Apps
tab on Autodesk Exchange.
ProductCode should be updated if the AppVersion is
changed. This is so upgrade installs work properly and
a notification is displayed for the upgrade when
loaded into AutoCAD.
On Windows, you can use the MSI installer Product-
Code or generate a GUID using an application such
as GuidGen.exe. There are also websites that allow
you to generate a GUID.
PackageContents.xml Format | 453