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
customization files; you can use macros and advanced entries such as DIESEL
expressions and AutoLISP routines.
However, you no longer perform customization tasks by creating or editing
MNU or MNS text files by hand. All customizations are done through the
program interface, in the Customize User Interface (CUI) Editor.
Menu Files Versus Customization Files
In releases prior to AutoCAD 2006, you customized the user interface by editing
an MNU or MNS file in an ASCII text editor such as Notepad. You manually
entered and verified customization data in the text file, which could be a
tedious and error-prone process. As a result, a simple syntax error (such as
mismatched parentheses) in the text file could invalidate the entire menu file,
leading you back to the text file to investigate where you made the error.
With the Customize User Interface (CUI) Editor, you drag a command to a
menu or toolbar or right-click to add, delete, or modify a user interface element.
The Customize User Interface (CUI) Editor displays element properties and a
list of options to choose from. This prevents you from creating syntax errors
or spelling mistakes that may have occurred when you manually entered text
in an MNU or MNS file.
The MNU and MNS files used in the past have been replaced with just one
file type, the XML-based CUIx file. CUIx is the successor to the CUI file format
which was introduced in AutoCAD 2006.
The XML-based format of the CUIx file allows the product to track
customizations. When upgrading to a future version of the program, all of
your customizations are automatically integrated into the new release. The
XML format also supports a backward-compatible customization file. This
means that you can view a CUIx file from a future version in the previous
release while preserving the customization data from the future version.
However, you cannot modify the future version's CUIx file in the previous
release. For more information about migrating customization data, see
Transfer
and Migrate Customization
on page 379.
The following table lists the menu files that previously shipped with the
product and shows how those files are mapped to AutoCAD 2012.
Menu files mapped to CUIx files
Description of changeIn Auto-
CAD 2012
DescriptionMenu file
An XML file that defines
most user interface ele-
CUIxASCII text file. In previous re-
leases, defined most user inter-
MNU
How Customization Has Changed | 97