Actually, there are a series of commands that act differently in AutoCAD 2009 and higher. However, the fix is easy.
Read up on the new initcommandversion function.
![]() |
|
![]() |
|
![]() |
|
![]() |
Actually, there are a series of commands that act differently in AutoCAD 2009 and higher. However, the fix is easy.
Read up on the new initcommandversion function.
R. Robert Bell
Design Technology Manager
Stantec
Opinions expressed are mine alone and do not reflect the views of Stantec.
Thanks Robert.
Please also read the following:
http://usa.autodesk.com/adsk/servlet...linkID=9240617
Please take a note:
There is an incorrect statement in the article
With the latest version, the fillet command options actually look like this:To use the newest command behavior, add the ^R control sequence before the command in the command macro. The following shows the same command macro using the new ^R control sequence:
^C^C^R_fillet;u; r;0.1;
The command prompt and options for the above command macro look like the following:
Current settings: Mode = TRIM, Radius = 0.1000
Select first object or [uNdo/Polyline/Radius/Trim/mUltiple]:
Therefore, my suggestion is that don't use shortcuts in your code, like U, P, and so on...Current settings: Mode = TRIM, Radius = 0.1000
Select first object or [Undo/Polyline/Radius/Trim/Multiple]:
ALWAYS use full word for the options to be executed.
"How we think determines what we do, and what we do determines what we get."
Sincpac C3D ~ Autodesk Exchange Apps
Computer Specs:
Dell Precision 3660, Core i9-12900K 5.2GHz, 64GB DDR5 RAM, PCIe 4.0 M.2 SSD (RAID 0), 16GB NVIDIA RTX A4000
This should be it:
http://usa.autodesk.com/adsk/servlet...linkID=9240617
C:> ED WORKING.... ▒
Last edited by RobertB; 2010-07-14 at 03:52 PM. Reason: Fixed quote
"How we think determines what we do, and what we do determines what we get."
Sincpac C3D ~ Autodesk Exchange Apps
Computer Specs:
Dell Precision 3660, Core i9-12900K 5.2GHz, 64GB DDR5 RAM, PCIe 4.0 M.2 SSD (RAID 0), 16GB NVIDIA RTX A4000