Leaderboard

Maybe something like this will help you: .................... (setq ename (car (entsel)) edata (entget ename '("*")) data (cdr (assoc -3 edata)) ) (foreach memb data (setq nlst (cons -3 (list (cons (car memb) nil)))) (setq ndata (subst nlst (assoc -3 edata) edata)) (entmod ndata) ) ....................

*s* remains for the future as a small device abandoned on the moon that, perhaps one day, will be used by the next visitor.

Hi @pkenewell I don’t use tangents. For straight segments, the geometry progresses or retreats based on the angular direction of the lateral segments of the selected one. For arc segments, in order to “link” them, progression and retreat are done based on the radius. The variable *s* is currently single-use if passed to the second part of the command, outside of GRREAD. The code is like a living being: it’s born with the idea of following a path, and along the way, it chooses a different route. So *s* was implemented with the intention of providing a complete solution within GRREAD, and along the way, the current solution was chosen instead.

I have mentioned several times, for some reason I struggle with manipulating polylines like this. When work slacks up, I am going to work at getting the hang of this. As of now it seems like witchcraft to me.

@GLAVCVS Nicely done! I'm still trying to get my head completely around this. I am trying to figure out how you are getting real-time coordinates when grread is not in tracking mode? i.e. (grread nil...) vs. (grread T...). I thought tracking mode had to be on to get real-time coordinates from the cursor. I guess you learn something every new every day, even old AutoLISP programmers like me that started back in the mid 90's. Also al trying to figure out the significance of flipping the *s* variable back and forth within the loop. Yours does react a little bit differently to ElpanovEvgeniy's original code, in the fact that his original code somehow keeps the tangency of segments adjacent to an arc segment if it exists.

That's not going to happen on here. Did you read the entire thread? Why do you need it as a .lsp? Tell us what it does and maybe there is a non-.fas version?

You're welcome.

After the XDATA deleted, you can check with command XDLIST, select that entity and you will get like this: "No Xdata associated with Application Name(s). Object has 16383 bytes of Xdata space available."

Hello Have you ever used this code and did it work for you?