Changes That May Affect Scripts
Changes to the following commands or system variables may affect pre-existing scripts:
- EXTEND
-
For the EXTEND command, if you do not select an object at the Select Objects to Extend prompt, you are now prompted to specify the opposite corner of a crossing window. This change may affect pre-existing scripts that call EXTEND and supply a pick point that selects no objects. You can fix legacy scripts by omitting points that do not select objects.
- INSERT
- MENULOAD
-
By default, the MENULOAD command loads only CUI files in AutoCAD 2006 or later releases. To load an MNU or MNS file in AutoCAD 2006 or later release, you must explicitly include the extension in the file name, as shown in the following example:
(command "menuload" "myMenu.mnu")
However, rather than changing your code, it is strongly recommended that you open your legacy menu files in AutoCAD 2009 before running applications that use them. AutoCAD 2009 automatically converts them to CUI files, and the CUI files are loaded by existing code that uses the file name without an extension
Legacy code that specifies an MNU, MNS, or MNC extension should be changed to reference a CUI file, and AutoCAD 2007-based applications should ship with CUI files, not MNU, MNS, or MNC files.
- TRIM
-
For the TRIM command, if you do not select an object at the Select Objects to Trim prompt, you are now prompted to specify the opposite corner of a crossing window. This change may affect pre-existing scripts that call TRIM and supply a pick point that selects no objects. You can fix legacy scripts by omitting points that do not select objects.
VBA scripts that run at startup should check whether the AutoCAD 2009 process is visible or invisible. If the process is invisible, the script should not execute, because the process may be performing background plotting or publishing operations. To check whether the AutoCAD 2009 process is visible or invisible, you can use the Visible property of the Application object in the AutoCAD 2009 Object Model.