I use COPYM frequently and found an unexpected behavior in ACAD 19 COPYM compared to ACAD 18. When I select an object and base point and then use polar tracking to select the 2nd point to be at the intersection of another target object (usually a line) the following happens: ACAD recognizes the object snap intersection (the "X" appears) but it won't insert the object at that intersection - it overrides the intersection that it clearly recognized and chooses to object snap to the MID or END of the target object. Aperature size seems to have no effect and the intersection can be the ONLY object snap point on the screen and ACAD 19 will still insert the copy object at MID or END (off screen). This procedure worked fine in ACAD 18. Does anyone else have this issue in ACAD 19?
Solved! Go to Solution.
I use COPYM frequently and found an unexpected behavior in ACAD 19 COPYM compared to ACAD 18. When I select an object and base point and then use polar tracking to select the 2nd point to be at the intersection of another target object (usually a line) the following happens: ACAD recognizes the object snap intersection (the "X" appears) but it won't insert the object at that intersection - it overrides the intersection that it clearly recognized and chooses to object snap to the MID or END of the target object. Aperature size seems to have no effect and the intersection can be the ONLY object snap point on the screen and ACAD 19 will still insert the copy object at MID or END (off screen). This procedure worked fine in ACAD 18. Does anyone else have this issue in ACAD 19?
Solved! Go to Solution.
Solved by chriscowgill7373. Go to Solution.
Do you think you can provide a screencast of it in 2018 and 2019? I just tested it in 2017, 2018, and 2019 and it seems to act the same way in all 3 versions
Christopher T. Cowgill, P.E.
AutoCAD Certified Professional
Civil 3D Certified Professional
Civil 3D 2022 on Windows 10
Please select the Accept as Solution button if my post solves your issue or answers your question.
Do you think you can provide a screencast of it in 2018 and 2019? I just tested it in 2017, 2018, and 2019 and it seems to act the same way in all 3 versions
Christopher T. Cowgill, P.E.
AutoCAD Certified Professional
Civil 3D Certified Professional
Civil 3D 2022 on Windows 10
Please select the Accept as Solution button if my post solves your issue or answers your question.
.... I just tested it in 2017, 2018, and 2019 and it seems to act the same way in all 3 versions
Yes, it's doubtful that this 20 year old lisp file has been modified. Although something inside of ACAD with which it reacts could have been changed I suppose.
;; ;; Copym.lsp - Multiple copy command with measure, divide and array capabilities. ;; ;; ;; Copyright © 1999 by Autodesk, Inc. ;;
.... I just tested it in 2017, 2018, and 2019 and it seems to act the same way in all 3 versions
Yes, it's doubtful that this 20 year old lisp file has been modified. Although something inside of ACAD with which it reacts could have been changed I suppose.
;; ;; Copym.lsp - Multiple copy command with measure, divide and array capabilities. ;; ;; ;; Copyright © 1999 by Autodesk, Inc. ;;
I stand corrected - ACAD 18 works the same way. The behavior seems common to everyone - that answers my question. I'm sorry for the confusion and thank you for the help.
I stand corrected - ACAD 18 works the same way. The behavior seems common to everyone - that answers my question. I'm sorry for the confusion and thank you for the help.
Can't find what you're looking for? Ask the community or share your knowledge.