LISP Debug, Repetitive copy & rotate
You don't get to specify a prompt in (ssget) -- it always supplies its own, which is "Select objects: " always in the plural. If you want to specify the prompt, even if only the same but in the singular, and if you always want to select only one object, use (entsel) instead, and apply (car) to the result to get the entity name of what you selected. Also, with (entsel) after you pick it, you're done, and don't need to tell it you're done as with (ssget).
Which raises the question: Do you, in fact, always want only one object? Such a thing could be done with multiple objects [and MOCORO can, too], though there's a little trick to it [Copy the selection in place and then Move the Previous selection, rather than Copying the selection directly to a new location, so that each time, the Previous selection is available without User input].
Either way, what you have going is not far off, but needs to account for completing the Rotate command, and it should include re-setting the 'basePoint' variable to use the 'targetPoint' variable value from the previous copy each time. It can be refined easily, if MOCORO doesn't suit your purpose well enough.
The commands will supply some of basically the same prompts for you, so you don't need to spell them out, and in fact don't need to put the target point into a variable at all. If you let that happen within the Copy command under its own prompt, instead of asking for it ahead of time, then you get to see what you're Copying drag with the cursor. Something like this [the only-one-object approach, and very lightly tested]?
(defun c:CRM (/ selObj basePoint); = Copy & Rotate Multiple
(if (setq selObj (car (entsel "\nSelect object: ")))
(progn
(setq basePoint (getpoint "\nBase point: "))
(while T ;; Infinite loop, will break on Esc
(command "copy" selObj "" basePoint pause)
;; Get the last created object
(setq selObj (entlast)); replace original selection
(setq basePoint (getvar 'lastpoint)); replace earlier one
;; Rotate the object interactively
(command-s "_.rotate" selObj "" basePoint "_reference")
)
)
)
)
It could be made to do things like verify that you actually selected something before proceeding, and could have all the usual enhancements added.
@michael_delouker wrote:
....
Would you have recommendations around assuming the specified reference angle as well as the second point prompts so the function could strictly rely on the mouse position? Im assuming we can set the initial as the previous references characteristics?
If you want to assume a zero reference angle each time, if that would serve for "so the function could strictly rely on the mouse position," you can just remove the "_referene" option entry from the end of the (command-s) function. Since the routine just leaves you in the command, you would still be able to call for that option yourself when needed.
If you want the previous ending rotation to be used as the base reference direction each time, something would need to be saved, but it's hard to know what. If the object is a Block or (M)Text, its rotation can be pulled. But if it's just about anything else, I'm not sure how to record the rotation. The location picked to set it for the latest round does not become "@" or (getvar 'lastpoint), but rather the rotation base point does, so there's no basis for reading the chosen rotation from command inputs. If the object is a Line, its direction could be pulled, but that would not always be the rotation picked for the latest round, and even when it is, it might read the opposite direction from what you want.
It should be possible by asking for points for the rotation, saving them to variables, but it may not be possible for you to see the rotation drag in the process. Would that be acceptable?
@michael_delouker wrote:
I believe the variety of the load with this function will just be with block objects....
If you want such a thing for use with only a Block, should it automatically use the insertion point of the Block as the base point for the Copying as well as the Rotating, or would you still want to specify the base point because it might not always be the Block's insertion point?
