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
For Local Deploy-
ment
For Download from
the Apps tab on
Autodesk Exchange
RequiredRequiredGlobal
RequiredRequiredLocal
ApplicationPackage Element
Each PackageContents.xml file must contain an ApplicationPackage element.
The ApplicationPackage element, in the form of XML Attributes, contains
general information about the plug-in. It also encapsulates other the element
types that help to define the contents of the plug-in.
An ApplicationPackage element can have any of the following attributes
attached to it:
DescriptionAttribute
PackageContents.xml format version number. The
value should always be 1.0 until a newer version of
the schema is introduced.
SchemaVersion
Application version number. AutoCAD uses this value
to determine if the installed version is the latest ver-
AppVersion
sion. If an updated version is available, the user is in-
formed and able to download and install the latest
version. It is recommended to use an application ver-
sion that includes major and minor values, such as
“1.0.0.0”.
Name of the plug-in author.Author
Plug-in name.Name
A localized plug-in name can be specified by combin-
ing Name with a locale code. See Supported Locale
Codes on page 461 for a full list of supported locale
codes.
Short description of the plug-in.Description
Localized descriptions can be specified by combining
Description with a locale code. See Supported Locale
452 | Chapter 7 Introduction to Programming Interfaces