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
NOTE Although this element is optional, it is possible that the plug-in might be
installed on Mac OSX or another system that the plug-in was not originally tested
on. Therefore, it is recommended that the element is used to control when the
plug-in can be loaded.
A RuntimeRequirements element can have any of the following attributes
attached to it:
DescriptionAttribute
Target operating system.OS
Supported values are ‘Mac’, ‘Win32’, or ‘Win64’. If
omitted, it is assumed the plug-in supports all operat-
ing systems. Multiple operating systems can be spe-
cified by separating the values with the '|' symbol.
(e.g. OS="Win32|Win64")
NOTE AutoLISP applications, .NET applications, and
CUIx files can be used across multiple operating sys-
tems.
Target AutoCAD or AutoCAD-based products.Platform
Should be used when using APIs specific to one of the
AutoCAD-based products that might not available in
AutoCAD or other AutoCAD-based products. Multiple
AutoCAd platforms can be specified by separating the
values with the '|' symbol.
NOTE The initial implementation of plug-ins cannot
differentiate AutoCAD from an AutoCAD-based
product, so the plug-in should support AutoCAD and
all AutoCAD-based products.
Defines the minimum AutoCAD release number the
set of components supports.
SeriesMin
The value can be a major version number (R18) or a
specific version (R18.1). The AutoCAD version number
can found in the Windows Registry or obtained with
the ACADVER system variable.
If this attribute and SeriesMax are not specified, it is
assumed all components are compatible with all
AutoCAD releases. If you omit this value, any version
before that specified by the SeriesMax attribute is al-
lowed.
456 | Chapter 7 Introduction to Programming Interfaces