How to make this pause work
@murmanator wrote:
.... Im trying to insert a command pause in between two snap functions in the middle of a pline command. The idea is to allow the user to make as many or as few clicks between the snaps. ....
If you mean an indeterminate number of picks to which the CENter Osnap does not apply as desired, between two picks to which it does apply, how is the routine supposed to know when you've picked as many as you want, and to feed in CENter Osnap for the next one?
The CMDACTIVE check can't accomplish that -- it keeps waiting until the entire command is completed, which is not as you describe if this is all inside one PLINE command.
I don't know of a way to do what you want [if I understand it correctly], in an automated way. I suspect you will just need to have the routine feed in the Osnap mode for the first pick, go around making your other picks, and call for the Osnap yourself when you get to where you need it again.
@murmanator wrote:
.... The first pick is snap to center, then an indeterminate number of picks, then the last pick is snap to center, or mid or whatever. Is there a way to do it by setting the osnap mode within the pline command? .... if you changed the osnap mode after the first pick it would be ready for the last pick, and all the other picks in between can just be in space somewhere (not snapped). ....
The indeterminacy is the problem. You can change the setting inside the command, but it can't be "ready for the last pick" when it has no way of knowing when that arrives, without your informing it in some way. So instead of doing whatever it takes to do that, you may as well just call for the Osnap yourself when you get to that point.
The only way I can imagine to do it is a two-stage approach: A routine could start PLINE and call for the Osnap for the first pick, turn off Osnap, then have a prompt built in asking you continue picking but to hit Enter when you're ready for the next pick to be the last with the designated Osnap mode. That Enter would actually end the first PLINE command, and then it could start another, from the last point, call up the Osnap mode and let you pick, end that second PLINE command, and then JOIN the second Polyline to the first. Does that sound worth pursuing?
Minimally tested and in simplest terms:
(defun C:PLCXC (/ pl); = PolyLine CENter-to-[whatever]-to-CENter
(command "_.pline" "_cen" pause); for first pick
(while (> (getvar 'cmdactive) 0)
(prompt "\nContinue Polyline and press ENTER when ready for last CENter-Osnap point: ")
(command pause)
); while
(setq pl (entlast))
(command
"_.pline" "@" "_cen" pause ""
"_.join" pl (entlast) ""
); command
(princ)
); defun
It lets you keep other running Osnap modes that you may have on, for other picks between the beginning and end, restricting it to CENter only for the first and last. If you don't want that, it could be made to turn Osnap off for the in-between picks, instead.
You can do all the options in the Polyline [look for its prompt above the one supplied by the routine], including widths and arc segments. But if you finish the first one with an arc segment, the second one will still be a line segment, so the result will not be a continuation as an arc segment as if it had been drawn all in one. If you need that, it could probably be accounted for.
@Sea-Haven wrote:
You can osmode to any combination you like so you could just set it to CEN MID END, these are discreet enough to not pick wrong point. ….
[That would often not be the case with an Arc or a partial Ellipse or a Polyline arc segment. Depending on the amount of angle it swings through, when the Osnap aperture is touching the curve itself, one endpoint or the other or the midpoint will very often be closer to the cursor location than the center is, and will therefore be what it snaps to.]
