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
Install Plug-in Packages
A package can be deployed using an installer, such as MSI, or manually copying
the files and folder structure to the ApplicationPlugins folder. For AutoCAD
Connect downloads, deployment of the package is done using an MSI installer.
Loading Plug-ins
By default, plug-ins are automatically registered with AutoCAD and when a
new plug-in is installed during the current session. The load behavior for
plug-ins is controlled with the APPAUTOLOAD system variable. When
APPAUTOLOAD is set to 0, no plug-ins are loaded unless the APPAUTOLOADER
command is used.
Uninstall Plug-in Packages
A package can be uninstalled by removing the appropriate folder with a .bundle
extension from the ApplicationPlugins folder. This can be accomplished by
offering an uninstall option with the original installer or to manually delete
the .bundle folder.
NOTE A plug-in downloaded from the Apps tab on Autodesk Exchange can also
be unistalled by going to Apps and then re-downloading the plug-in. When the
download completes, you are prompted to uninstall the plug-in.
Quick Reference
Commands
APPAUTOLOADER
Lists or reloads all plug-ins in the application plug-in folder.
System Variables
APPAUTOLOAD
Controls when plug-in applications are loaded.
PackageContents.xml Format
The PackageContents.xml file contains information about the application
package, including information about the developer that authored it.
PackageContents.xml Format | 449