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
Menu files mapped to CUIx files
Description of changeIn Auto-
CAD 2012
DescriptionMenu file
ments. The main CUIx file,
acad.cuix, is automatically
face elements. The main
MNU file, acad.mnu, was
loaded when you start the
product.
automatically loaded when
you started the product.
Partial CUIx files can be
loaded or unloaded as you
Partial MNU files could be
loaded or unloaded as you
need them during a drawing
session.
needed them during a draw-
ing session.
An XML file that defines
most user interface ele-
CUIxSource menu file. Was the
same as the MNU ASCII text
MNS
ments. The main CUIx file,file but did not contain com-
ments or special formatting. acad.cuix, is automatically
loaded when you start the
product.
Partial CUIx files can be
loaded or unloaded as you
need them during a drawing
session.
An XML file that defines
most user interface ele-
CUI
x
Compiled ASCII text file.
Contained command strings
MNC
ments. The main CUIx file,and syntax that defined the
acad.cuix, is automaticallyfunctionality and appearance
of user interface elements. loaded when you start the
product.
Partial CUIx files can be
loaded or unloaded as you
need them during a drawing
session.
No change.MNLMenu LISP file. Contains
AutoLISP expressions that are
MNL
used by the user interface
elements.
No change.MNRMenu resource file. Contains
the bitmaps that are used by
the user interface elements.
MNR
98 | Chapter 4 User Interface Customization