Leaderboard

My own advice for your specific issue is not to use a solid hatch and print it as black unless absolutely necessary. Personally, the only solid hatches I include in my final prints are one of 3 colors - 251, 252 or 253 (shades of grey). But in my case the only reason I sometimes use grey solid hatches is to provide additional context or highlight something specific to make it pop in the final print. IMO, it is more pleasing to the eye, uses less toner, and allows you to achieve the same result of making something specific "pop", if you will. Using solid hatches as shades of grey Is a trick I learned back in '04 and it can make for a really nice looking drawing - which is like half the battle. -ChriS

Glad I could help.

They both change properties of an object, options at the command line are the same just slightly different to get there. However CHANGE will also let you select a new change point which will affect lines and circles (may be other objects), with the line you can change the start or end point depending on where you pick on screen. With circle it will change the size of the circle. I have used CHANGE for lines for my whole career to change lines that were not drawn on ortho to ortho. With Ortho set on, pick one or more lines, start CHANGE and then pick a point on screen or use perp osnap and pick a line. If the lines are far enough apart some lines may not end up where you expect and instead will be 90 degrees from where you hoped but once you know how it will works it is a very quick way to bring lines of odd angles to ortho. Say some lines were drawn 1 degree off of ortho (or 10 degrees or whatever) and you have a line you want them to extend to and be perpendicular to; start CHANGE, pick all the lines, with Ortho on, snap to the target line and the ones picked will be perpendicular to that line and end on that line.

Personally, I leave the properties window open on the side at all times to make life easier. This way the properties are also all in one place and easily clickable instead of having to run through the step by step process in the command line. But if it works for you, stick with it. -ChriS

Question is the Ent-pc variable a vla-object? If so - this looks like a job for (vl-catch-all-apply 'function list) Your Example would be something like: (setq res (vl-catch-all-apply 'vla-get-area (list ent_pc))) (if (vl-catch-all-error-message res) (alert "Somthing went Wrong - Try again."))

Vakadi, Does this one from Lee, do what you require? http://www.lee-mac.com/outlineobjects.html

CHANGE seems to allow a change to a point before going into the CHPROP command. Try it out on a few different types of objects and watch the command line to find out for yourself or try the help files for a description of the commands.

2 things come to mind. If hatch causes a error message you need to trap that and work out what to do next, the If will find the prior hatch so add it twice. Error trapping not my best subject. The other is to have a max area size if that is at all possible.

@enthralled Another to try .. should be quite a bit faster on large selection sets. (defun c:foo (/ a n s x) ;; RJP » 2021-01-08 (cond ((setq s (ssget '((0 . "LWPOLYLINE")))) (setq s (vl-remove-if 'listp (mapcar 'cadr (ssnamex s)))) (setq s (mapcar '(lambda (x) (list (vlax-curve-getstartpoint x) (vlax-curve-getendpoint x))) s)) (setq s (vl-sort (apply 'append s) '(lambda (r j) (< (car r) (car j))))) (setq s (vl-sort s '(lambda (r j) (< (cadr r) (cadr j))))) (while (car s) (setq a (car s)) (setq s (cdr s)) (setq n 0) (while (equal a (car s) 1e-8) (setq n (1+ n)) (setq s (cdr s))) (entmake (list '(0 . "CIRCLE") (cons 10 a) '(8 . "Circle") '(40 . 5) (cons 62 (if (> n 1) 1 5)))) ) ) ) (princ) ) A wheeeee bit faster on 100x the OP sample drawing