Leaderboard

That has fixed it and back working perfectly again, i cant thank you enough!!!

use (car (nentsel)) for that.

Witchcraft!! That is SO cool!! Thank you Sir

Winner!! That was my original design intent. Thank you so very much!! = In addition, I now have different options for a working solution. I appreciate you guys and your assistance. Thank you ALL so very much!

Hello, fuccaro thank you very much it works really well. a big thank-you you are fantastic. I worked on it all evening without success. Sincerely Philip

What would be helpful is to get all the settings so could make a table style, save them into say a csv file, then a make Tablestyle could be ran, getting a table to match a client setting involves many properties. list of methods for a table.txt

A train driver is an engineer, should you talk to that person ?

@Dien nguyen There is also THIS.

Then I would follow the advice of the engineers. I am not an engineer, but I did play one on TV once. LOL!

Interesting and thanks, this is one I am going to keep for myself so worth me taking the time over it, I should have time this week to look at the very small lines and small gaps. Having a quick look, some of the circles are not -quite- identical (overlaid one on top of another, overkill, and there are some lines left from both) which might explain that.

Good to hear it. I may have updated the program since this post. When I get home, I will check and if so, upload a new copy.

Just a comment or 2, a closed object when offset to outside the area will be bigger than original so a +v or -ve can be implied, just check and erase if required uses VLA-offset. Hint recent post forums/autodesk. an open object like a line or pline you pick near an end this implies the direction of the line a simple little defun can check. You get used to it, yes vertical lines etc. Just for illustration needs line or pline handled differently. (setq ent1 (entsel "\nPick line 1 TP end ")) (setq pt1 (cadr ent1)) (setq ent1g (entget (car ent1))) (setq pt10 (cdr (assoc 10 ent1g))) (setq pt11 (cdr (assoc 11 ent1g))) (setq d1 (distance pt1 pt10)) (setq d2 (distance pt1 pt11)) (if (> d1 d2) ; swap offset +ve -ve value ...... )

Not quite - there are two elements that you first need to ascertain: the name of the dynamic block parameter that you need to change, and the data type of the parameter value (so that you can prompt the user for the appropriate data). Once you have this information, you can use a program such as the following to set the parameter value (you will need to adjust the property name and user prompt to suit the above): (defun c:dynamo2 ( / i o p s v ) (setq p "YourPropertyName") (cond ( (not (setq s (ssget "_X" '((0 . "INSERT") (410 . "~Model"))))) (princ "\nNo blocks found in Paperspace.") ) ( (/= "" (setq v (getstring "\nEnter the desired value: "))) (repeat (setq i (sslength s)) (setq i (1- i) o (vlax-ename->vla-object (ssname s i)) ) (if (= :vlax-true (vla-get-isdynamicblock o)) (LM:setdynpropvalue o p v) ) ) ) ) (princ) ) (vl-load-com) There is no need to modify the code for my functions in any way, and I would also prefer if you retained the code headers.