Draw line from a list of points
Upon defining a function such as the following to construct a line from two supplied points:
(defun drawline ( p q ) (entmake (list '(0 . "LINE") (cons 10 p) (cons 11 q))))
You can evaluate the function with the successive points in your list using a mapcar expression in the following way:
(mapcar 'drawline lst-pts (cdr lst-pts))
At the risk of being scoffed at by those with an irrational fear of the (command) function:
(command "_.line")
(foreach pt lst-pts (command "_non" pt))
(command "")
(setq lst-pts '((-2495.52 -924.94 0.0)
(-2397.64 -924.672 0.0)
(-2297.97 -889.794 0.0)
(-2200.08 -810.342 0.0)
(-2108.74 -776.927 0.0)
(-1997.02 -818.492 0.0)))
;; Alan Pizzamando
(mapcar (function (lambda (a b) (entmakex (list '(0 . "LINE") (cons 10 a) (cons 11 b)))))
lst-pts
(cdr lst-pts)
)
@carlos_m_gil_p wrote:
....
Hi @Kent1Cooper , if you knew about this option, but wanted to avoid the commands, due to errors. ....
[What errors? You may have fallen for the irrational-fear brainwashing. I use (command) functions all over the place in lots of routines, and they never result in errors.]
I'm not sure that I follow the 'brainwashing' and 'irrational fear' sentiments, but performance considerations and control over object properties aside, command calls certainly have their place in scenarios where it makes sense to leverage AutoCAD functionality; personally I generally try to avoid dependence on commands where possible, mainly due to the possibility of the command prompts changing with each AutoCAD release.
@carlos_m_gil_p wrote:
(defun d-line (lst) (foreach pt lst (ent-linea pt)))
As for your sub-function
(defun d-line (lst / p)
(foreach pt lst-pts
(if p
(draw-line p pt)
)
(setq p pt)
)
)HTH
@carlos_m_gil_p wrote:
Hi @Kent1Cooper , the issue is that sometimes I get a command or command-s prompt, that's why I avoid using it.
....
If you're talking about the error suggestion to change (command) functions to (command-s), that happens only if you use a (command) function inside an *error* handler [without taking another step that the message describes], and only if the *error* handler is triggered [whether by an actual error happening or by cancelling with the ESCape key], and only in versions newer than I think Acad2015. An error that triggers the *error* handler [and therefore that suggestion] could be caused by something incorrect in the inputs to a (command) function in the code, or by myriad other possible problems, but never by the mere fact that the (command) function is what was used to do something. So change those instances inside *error* handlers, as the message suggests. That's one of the limited situations where (command) should be avoided, but is not a reason to avoid it elsewhere.
@Anonymous wrote:
I know solved but why not make the points a pline.
That can be done with the approach in Message 3, by simply adding one letter, changing "_.line" to "_.pline", with the proviso that the current PLINEWID width setting will be used, which could be other than 0 [you might sometimes want it other than 0].
[The possibility of wanting to Close it can be incorporated, but wasn't because of the nature of the example set of points.]