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
Quick Reference
Commands
NETLOAD
Loads a .NET application.
Install and Uninstall Plug-In Applications
The plug-in auto loader mechanism allows for the easy deployment of custom
applications using a package format.
The package format is a common folder structure than contains the extension
.bundle in its name and has an XML file that defines the various components
of the plug-in. By deploying custom applications as a BUNDLE, it makes it
easier to target multiple operating systems and product releases since the
parameters of your plug-in are defined in the XML file of the package. A
BUNDLE can be used as a replacement to creating complex installer scripts
when deploying a plug-in.
The plug-in defined by each package is loaded into AutoCAD by placing it in
one of the ApplicationPlugins folders on your local drive. There are two different
ApplicationPlugins folders that you can use:
Product Install folder
■ <drive>:\Program Files\Autodesk\ApplicationPlugins
User Profile folder
■ (Windows XP) <drive>:\Documents and Settings\<user name>\Application
Data\Autodesk\ApplicationPlugins
■ (Windows Vista or Windows 7) <drive>:\Users\<user
name>\AppData\Roaming\Autodesk\ApplicationPlugins
When AutoCAD starts, both ApplicationPlugins folders are checked for plug-in
applications. The packages found are automatically registered and loaded
based on the metadata in the XML file of each package.
448 | Chapter 7 Introduction to Programming Interfaces