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
element of the same type in the main CUIx file, or it can come from a partial
CUIx file.
You cannot swap interface elements that are of different types (menus and
mouse buttons, for example). However, within a given type, you can swap
any user interface element for any other element.
NOTE Swapping can lead to some strange behavior for tablet menus, because
they typically have a different number of macros.
Use the following syntax in a macro to swap elements:
$section=customizationgroup.menuname
The following describes each section of the macro syntax for swapping
elements:
Macro syntax for swapping elements
$ Loads an interface element
section Specifies the element type. Valid names are:
A1-A4 for Aux menus 1 through 4
B1-B4 for mouse buttons 1 through 4
P0-P16 for pull-down menus 0 through 16
I for the image tile menu
S for the screen menu (obsolete in and later)
T1-T4 for tablet menus 1 through 4
customizationgroup Specifies the customization group that menuname is a
member of (not necessary if menuname is in the main CUIx file).
menuname Specifies which section or submenu to insert. It is the main label
or alias for the section to load
A pull-down menu can be present either in the menu bar or on the active
shortcut menu but not both.
Quick Reference
Commands
CUI
Manages the customized user interface elements in the product.
Create Macros | 161