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
(through the loading of partial CUIx files), the following syntax will not work
in all cases.
(menucmd "P1.2=~")
This syntax relies on the location of the menu item and does not work if a
new item is inserted before POP1 by the CUILOAD command.
Menu item numbering is consecutive regardless of the hierarchy of the menu.
To make it easy for an item to address itself regardless of its location in the
menu hierarchy, use these forms:
$P@.@=xxx References the current or most recently chosen command.
$P@.n=xxx References item n in the current or most recently chosen menu.
AutoLISP Access to Label Status
The AutoLISP menucmd function accepts $Pn=xxx command strings but without
the leading $. For these functions, the xxx portion of the command string can
have special values.
Pn.i=? Returns the current disabled and marked status for the specified item
as a string (for example, ~ for a disabled item, !. for an item with a check
mark, and "" for an item that is neither grayed out nor marked).
Pn.i=#? Returns the same type of string as described for Pn.i=?, but with the
Pn.i= prefix. This is useful in conjunction with the @ forms, because the actual
menu and item number are returned.
For example, if the fifth item in the POP6 section is disabled, the following
menucmd code returns the following string values.
(menucmd "P6.5=?") returns "~"
(menucmd "P6.5=#?") returns "P6.5=~"
See “Use of AutoLISP in Macros” in the AutoLISP Developer's Guide.
Quick Reference
Commands
CUI
Manages the customized user interface elements in the product.
Pull-down and Shortcut Menus | 289