All Activity

Why not use (setvar 'osmode 512) ; as per NEAREST (setq pt1 (getpoint "\nSelect the first break point: ") ;; Entering the first break point pt2 (getpoint "\nSelect the second break point: ") ;; Entering the second break point ep nil ) So point will be at select entity

use this PEDIT WAY (command "._PEDIT" topline "_J" "all" "" "" ) ;topline infilHL bottomline infilHR "" "_j" "" "")

Please upload this defun (savevartoold) (infilpanellayer)

Read up on cond. better way to test/decide what block to insert. (cond ((and (>= dist1 145) (< dist1 220)) (command "-insert" "*Infil_sq_1" p7 "" "" "") ) ((and (>= dist1 220) (< dist1 295)) (command "-insert" "*Infil_sq_2" p7 "" "" "") ) ((and (>= dist1 295) (< dist1 370)) (command "-insert" "*Infil_sq_3" p7 "" "" "") ) ... ((and(>= dist1 1195) (< dist1 1270)) (command "-insert" "*Infil_sq_15" p7 "" "" "") ) (T ;if all other condtions fail (alert "\nDistance Greater than 1270") ) )

Hi All. This time I have included my files to give you a better idea of what i'm trying to acheive Thanks for the ideas. I have used the PEDIT approach and it has almost worked. It joins 3 of the entities but not the 4th. The program runs right through. Any ideas why the 4th entity won't join?? Ive included my DWG file for you to have a look and also my lisp routine. The bulk of the routine works well its just the join command Regards tony Horozontal Infil.lsp Infil Panels AutoLisp Test.dwg

I got to thinking.. if blocks represent parts and multiple similar Parts exists the same assigned number should be same for similar parts. So after adding Part_Number attribute could the lisp runs the below results? (graphically like column order in a table, but the way the order lisp sorts). I see issues if Part_Number and other Sort Orders values don't match when hoping for blocks with same part number to be assigned same Dataport Number. So there would need to be a warning if that occurs. Hope this makes sense. DATAPORT_NUMBER --> order by--> | Sort_Order | Sort_Order2 | Sort_Order3 | <--Part_Number "001" --> "1000" "001" "" <-- "DD3" "002" -->"1100" "003" "" <-- "PIE" "002" -->"1100" "003" "" <-- "PIE" "003" -->"1200" "1" "" <-- "APPLE" "004" -->"1200" "001" "Tomorrow" <--"PEAR" "005" --> "1200" "001" "Tomorrow"<--"PEACH" "005" -->"1200" "001" "Tomorrow" <--"PEACH" "006" -->"1200" "001" "Yesterday" <--"CHERRY" "007" -->"1250" "" "" <--Box "007" -->"1250" "" "" <--Box "008"-->"1350" "" "" <- Chocolates "009" -->"1400" "" "" <--Pickles etc PNO TEST-LSP FOR NUMBING3.dwg

I got to thinking.. if blocks represent parts and multiple similar Parts exists the same assigned number should be same for similar parts. So after adding Part_Number attribute could the lisp runs the below results? (graphically like column order in a table, but the way the order lisp sorts). I see issues if Part_Number and other Sort Orders values don't match when hoping for blocks with same part number to be assigned same Dataport Number. So there would need to be a warning if that occurs. Hope this makes sense. DATAPORT_NUMBER --> order by--> | Sort_Order | Sort_Order2 | Sort_Order3 | <--Part_Number "001" --> "1000" "001" "" <-- "DD3" "002" -->"1100" "003" "" <-- "PIE" "002" -->"1100" "003" "" <-- "PIE" "003" -->"1200" "1" "" <-- "APPLE" "004" -->"1200" "001" "Tomorrow" <--"PEAR" "005" --> "1200" "001" "Tomorrow"<--"PEACH" "005" -->"1200" "001" "Tomorrow" <--"PEACH" "006" -->"1200" "001" "Yesterday" <--"CHERRY" "007" -->"1250" "" "" <--Box "007" -->"1250" "" "" <--Box "008"-->"1350" "" "" <- Chocolates "009" -->"1400" "" "" <--Pickles etc PNO TEST-LSP FOR NUMBING3.dwg

I created a new post for this topic. Attributes be added to factor the outcome of Incremental numbers.

@GLAVCVS Thank you very much, as always, you are very attentive to details. It is very convenient that the functions work in a loop and a dashed line is created immediately. "But in the end, I decided to spend a little time improving the code". The code has been improved by 100 percent!

Yes.. the layout you show is what I was thinking of. Attached here is the PNO lisp from earlier in this thread that I was hoping could be altered to do that. Thanks pno.LSP

Thanks Bigal for looking into this. The goal is to have incremental number input into Attribute "Port_Number" based on level of priority..Sort_Order then Sort_Order2 then Sort_order3. The first and second attributes would always have a value, but the third attribute may at time be empty. Ideally when many blocks that share the same values in the 1st 2 attributes, the lisp looks to the 3rd for direction for the next incremental number assignment.

To Admin this is really a new task, as its the posters first post. Does not match this post. You can sort multiple attributes in a order of attributes. I have some thing that works for up to 5 attributes deep. It pads missing attrbute values, so can have say 1 or up to 4 attribute values. I need some time to have a look at say add a "002" block and find highest attribute value of existing blocks. ("DATAPORT NUMBER" "001" "1000" "001" "") ("DATAPORT NUMBER" "002" "1200" "002" "") ("DATAPORT NUMBER" "002" "1200" "002" "Tomorrow") ("DATAPORT NUMBER" "002" "1200" "002" "Yesterday") ("DATAPORT NUMBER" "003" "1200" "001" "") ("DATAPORT NUMBER" "004" "1350" "" "") ("DATAPORT NUMBER" "005" "1400" "" "") ("DATAPORT NUMBER" "006" "1500" "" "") ("DATAPORT NUMBER" "007" "1600" "" "") ("DATAPORT NUMBER" "008" "1700" "" "") ("DATAPORT NUMBER" "009" "1800.9" "" "") ("DATAPORT NUMBER" "010" "1900" "" ""))

Another important detail: in the circles, the resulting arc that will be modified depends on whether the cut points are indicated in a clockwise or counterclockwise direction. If they are selected in the opposite direction from what is needed to obtain the desired result, it can be immediately switched by pressing TAB key (as indicated in the command line).

I think I read your first explanation too quickly. I also thought about keeping the main part of your code to avoid overcomplicating my answer. But in the end, I decided to spend a little time improving the code. Here's another option for doing this task. One possible difference (or not) with the other options discussed in this thread is that the cut points may or may not be on the object to be cut: when they aren't, it will calculate the perpendicular point. Another small difference is that here, you're still required to first select the object to be modified to avoid the problem of cases where several objects coincide at the same point. (defun c:Br2ptReplDash (/ para tl ss pt1 pt2 p1 p2 ent vlae ep to c r eumk entdata newent entUlt osmant ecoA lstChg lstR lent1 lent pIni pFin dameSeg *troca* erroria errores error0 ) (defun erroria () (defun errores (mens) (setq *error* error0) (command-s "._undo" "_1") (prin1) ) (setq error0 *error* *error* errores ) ) (defun dameSeg (e p1 p2 / vlae pIni pFin rg) (setq pIni (vlax-curve-getPointatParam (setq vlae (vlax-ename->vla-object e)) (vlax-curve-getStartParam vlae)) pFin (vlax-curve-getPointatParam vlae (vlax-curve-getEndParam vlae)) rg (* (getvar "PICKBOX") (/ (getvar "VIEWSIZE") (cadr (getvar "SCREENSIZE"))) 1.01) ) (if (and (or (equal p1 pIni rg) (equal p1 pFin rg) ) (or (equal p2 pIni rg) (equal p2 pFin rg) ) ) T ) ) (defun grreadea (/ para lr ) (while (not para) (princ "\rPress TAB to switch modifications, Select next object to split or RIGHT CLICK to EXIT...") (setq lr (grread T 4 2)) (cond ((= (car lr) 2) (cond ((= (cadr lr) 9) (setq *troca* (not *troca*)) (entmod (append (if *troca* lent lent1) lstChg)) (entmod (append (if *troca* lent1 lent) lstR)) ) ) ) ((= (car lr) 25) (setq para 0 ep nil) ) ((= (car lr) 3) (if (listp (cadr lr)) (setq ep (nentselp (cadr lr)) ep (if (wcmatch (cdr (assoc 0 (entget (car ep)))) "*LINE,ARC,CIRCLE") ep) para (if ep T) ) ) ) (T (if (/= (car lr) 5) (print lr) )) ) ) para ) (erroria) (setq osmant (getvar "OSMODE") ecoA (getvar "CMDECHO") eumk nil tl "DASHED2" tl (if (tblsearch "LTYPE" tl) tl (progn (vlr-beep-reaction) (alert (princ (strcat "\n*** Linetype " tl " not found. It will be instead CONTINUOUS"))) "CONTINUOUS" ) ) lstChg (list '(8 . "0") ; the default layer (cons 6 tl) ; line type '(48 . 0.25) ; thickness '(62 . 84) ; color ) ) (setvar "CMDECHO" 0) (while (and (not para) (or ep (setq ss (SETVAR "NOMUTT" 1) ss (princ "\nSelect object to trim (RIGH CLICK to EXIT)...") ss (ssget "_+.:E:S" '((0 . "*LINE,POLYLINE,CIRCLE,ARC"))) ) ) ) (SETVAR "NOMUTT" 0) (setq entUlt (entlast)) (princ "\nSelect the object to split...") (setq ent (if ep (car ep) (ssname ss 0)) lstR (list (cons 6 (if (assoc 6 (entget ent)) (cdr (assoc 6 (entget ent))) "BYLAYER")) (cons 48 (if (assoc 48 (entget ent)) (cdr (assoc 48 (entget ent))) 1.0)) (cons 62 (if (assoc 62 (entget ent)) (cdr (assoc 62 (entget ent))) 256)) ) ) (setq pt1 (getpoint "\nSelect the first break point: ") ;; Entering the first break point pt2 (getpoint "\nSelect the second break point: ") ;; Entering the second break point ep nil ) (vla-startUndomark (vla-get-activeDocument (vlax-get-acad-object))) ;; Checking the object type and performing the split (cond ((wcmatch (setq to (cdr (assoc 0 (entget ent)))) "*LINE") ;; break polyline (setq pt1 (vlax-curve-getClosestPointTo (vlax-ename->vla-object ent) pt1) pt2 (vlax-curve-getClosestPointTo (vlax-ename->vla-object ent) pt2) ) (command "_.BREAK" ent pt1 pt2) (command "_.LINE" pt1 pt2 "") (entmod (append (ENTGET (ENTLAST)) lstChg)) ) ((= to "CIRCLE") ;; break the circle (setvar "OSMODE" 0) (entmake (entget ent)) (command "_.BREAK" ent pt1 pt2) (command "_.BREAK" (entlast) pt2 pt1) (setq lent (entget ent)) (entmod (append (setq lent1 (entget (entlast))) lstChg)) (setq para (= 0 (grreadea))) ) ((= to "ARC") ;; break the arc (setvar "OSMODE" 0) (setq ;ent1 (entmake (entget ent)) pIni (vlax-curve-getPointatParam (setq vlae (vlax-ename->vla-object ent)) (vlax-curve-getStartParam vlae)) pFin (vlax-curve-getPointatParam vlae (vlax-curve-getEndParam vlae)) pt1 (polar (setq c (cdr (assoc 10 (setq lent (entget ent))))) (angle c pt1) (setq r (cdr (assoc 40 lent)))) pt2 (polar c (angle c pt2) r) ) (command "_.BREAK" ent pt1 pt1) (if (equal (car (nentselp pt2)) (setq ent1 (entlast))); SI P2 EST脕 SOBRE LA NUEVA ENTIDAD CREADA (command "_.BREAK" ent1 pt2 pt2) (command "_.BREAK" ent pt2 pt2) ) (entmod (append (entget (if (dameSeg (setq ent2 (entlast)) pt1 pt2) ent2 ent1)) lstChg)) ) (T (prompt "An object of an unsupported type.") ) ) (vla-EndUndomark (vla-get-activeDocument (vlax-get-acad-object))) (setq eumk T) (setvar "OSMODE" OSMANT) ) (if ecoA (setvar "CMDECHO" ecoA)) (if (not entUlt) (princ "\nObjects are not selected.")) (princ) )

thanks.

RE: PNO lisp: Can additional attributes be added to factor the outcome of Incremental numbers? When I review the PNO lisp I keep wondering, can the results of assigned incremental number in "Port_Number" attribute be secondarily ordered by a 2nd attribute "Sort_Order2" value after the 1st "Sort-Order" value? AND possibly by 3rd priority sort of 3rd attribute's alphabetic value in a 3rd attribute "Sort_Order3"? These option, if possible, would allow more control of the assigned incremental numbers. Attached is blocks as example. PNO TEST-LSP FOR NUMBING2.dwg

There are some LISPs/programs out there. AutoCAD Architecture FREE toolset has the AECLINEWORKSHRINKWRAP command. Or... Polyline Outline (Advanced) | Lee Mac Programming. Maybe this... TotalBoundary • Outline creation tool - Programs and Scripts - AutoCAD Forums Maybe something in this thread...

There are some LISPs/programs out there. AutoCAD Architecture FREE toolset has the AECLINEWORKSHRINKWRAP command. Or... Polyline Outline (Advanced) | Lee Mac Programming. Maybe this... TotalBoundary • Outline creation tool - Programs and Scripts - AutoCAD Forums Maybe something in this thread...

Slight different way of looking at this - back to OPs original problem of how to select the entities - instead of insert and explode, load the block into the drawing and grab the entities it contains from there. The block doesn't need to be inserted, that can come shortly. This will insert the exploded block (for most simple entities, not tested fully) The selection set MyAllSS contains all the inserted entities, so I think (command "join" .... ) will join everything together You'll have to adjust the BlockName list. (defun c:SSBlockEntities ( / BlockName acount MyEnts MyAllSS MySS MyEnt NewEnt) ;;Sub routines ;;https://forums.autodesk.com/t5/visual-lisp-autolisp-and-general/how-to-select-all-entities-inside-of-a-block/td-p/10284294 (defun blockcomponents ( blk / ent rtn ) (if (setq ent (tblobjname "block" blk)) (while (setq ent (entnext ent)) (setq rtn (cons ent rtn)) ) ) (reverse rtn) ) ;; End subroutines (setq BlockName '( "CircuitBreaker" "CT")) ;; Block Names to assess (setq MyAllSS (SSAdd)) ;; Blank Selection set - all entities, all blocks (foreach n BlockName (setq MySS (SSAdd)) ;; Blank Selection set (setq acount 0) ;; A counter (setq MyEnts (blockcomponents n)) ;; Entity list for block (while (< acount (length MyEnts)) ;; Loop this block (setq MyEnt (entget (nth acount MyEnts))) ;; nth entity description (setq NewEnt (entmakex MyEnt)) ;; Make a new entity (ssadd NewEnt MySS) ;; Add entity to selection set (ssadd NewEnt MyAllSS) ;; Add entity to selection set - all entities, all blocks (setq acount (+ acount 1)) ;; Increase Loop ) ; end while ;; Or do command 'Move' and 'rotate' on MySS selection set here: (command "move" MySS "" '(0 0 0) pause "") (command "rotate" MySS "" (getvar 'lastpoint) pause) ) ; foreach n (princ) ; exit quietly )

This code works, but you need to remember that for a CIRCLE and an ARC, you need to select points clockwise. ;; AutoLISP, which allows you to select objects (line, polyline, circle, arc), ;; break them at two points and replace the selected section with a dashed line with the specified parameters ;; **CIRCLE and ARC needs to be selected in an anti clockwise direction. Clockwise gives a big arc** ;; https://www.cadtutor.net/forum/topic/98693-break-an-object-at-2-points-and-replace-the-properties-of-the-line/ ;; The source code of the author is BIGAL (defun c:brkobjLN-CIR ( / ent ent1 pt1 pt2 type obj1 rad cenpt ) (setq oldsnap (getvar 'osmode)) (setvar 'osmode 183) (setq ent (entsel "Pick object to break at: ")) (if ent (progn (setq ent1 (car ent)) (setq pt1 (getpoint "Pick first point: ")) (setq pt2 (getpoint "Pick second point: ")) (setq type (cdr (assoc 0 (entget ent1)))) (command "_.break" ent1 pt1 pt2) (cond ((or (= type "LINE") (= type "LWPOLYLINE")) (command "_.line" pt1 pt2 "") (command "_.chprop" (entlast) "" "_LT" "DASHED2" "_C" 5 "_LW" 0.25 "_S" 10 "") ) ((= type "ARC") (setq obj1 (vlax-ename->vla-object ent1)) (setq rad (vlax-get obj1 'radius)) (setq cenpt (vlax-get obj1 'center)) (command "_.arc" pt1 "_C" cenpt pt2) (command "_.chprop" (entlast) "" "_LT" "DASHED2" "_C" 5 "_LW" 0.25 "_S" 10 "") ) ((= type "CIRCLE") (setq obj1 (vlax-ename->vla-object ent1)) (setq rad (vlax-get obj1 'radius)) (setq cenpt (vlax-get obj1 'center)) (command "_.arc" pt1 "_C" cenpt pt2) (command "_.chprop" (entlast) "" "_LT" "DASHED2" "_C" 5 "_LW" 0.25 "_S" 10 "") ) ) ) ) (setvar 'osmode oldsnap) (princ) )

Thanks, at the stage of setting the properties of the line, this does not happen automatically, but requests for color, layer, line weight, and so on appear on the command line...

Found some time have a look at this not finished but draws tabs. Save Multi getvals.lsp to a support path. ; https://www.cadtutor.net/forum/topic/98697-autocad-join-command/ ; Draw tabs on a rectang ; By AlanH Sept 2025 (defun c:wow ( / oldsnap pt1 pt2 pt3 pt4 pt5 pt6 ssadd) (setq oldsnap (getvar 'osmode)) (setvar 'osmode 0) (if (not AH:getvalsm)(load "Multi Getvals.lsp")) (setq ans (AH:getvalsm (list "Enter values " "length" 5 4 "200" "Width " 5 4 "200" "Tab height" 5 4 "20" "Tab width" 5 4 "20" "Tab edge dist" 5 4 "15"))) (setq len (atof (nth 0 ans)) ht (atof (nth 1 ans)) tabht (atof (nth 2 ans)) tabwid (atof (nth 3 ans)) tabedge (atof (nth 4 ans)) ) (setq pt1 (getpoint "\nPick point bottom left ") pt2 (mapcar '+ pt1 (list len 0.0 0.0)) pt3 (mapcar '+ pt1 (list len ht 0.0)) pt4 (mapcar '+ pt1 (list 0.0 ht 0.0)) ) (command "rectang" pt1 pt3) (setq ent1 (entlast)) (setq pt5 (mapcar '+ pt1 (list 0.0 tabedge 0.0))) (setq pt6 (mapcar '+ pt1 (list 0.0 (+ tabedge tabwid) 0.0))) (command "Break" ent1 pt5 pt6 ) (setq pt7 (mapcar '+ pt5 (list (- (- tabwid (/ tabht 2.0))) 0.0 0.0))) (setq pt8 (mapcar '+ pt6 (list (- (- tabwid (/ tabht 2.0))) 0.0 0.0))) (setq mp (mapcar '* (mapcar '+ pt7 pt8) '(0.5 0.5))) (command "pline" pt6 pt8 "a" pt8 "CE" mp pt7 "L" pt5 "") (setq pt5 (mapcar '+ pt4 (list 0.0 (- tabedge) 0.0))) (setq pt6 (mapcar '+ pt4 (list 0.0 (- (+ tabedge tabwid)) 0.0))) (command "Break" ent1 pt5 pt6 ) (setq pt7 (mapcar '+ pt5 (list (- (- tabwid (/ tabht 2.0))) 0.0 0.0))) (setq pt8 (mapcar '+ pt6 (list (- (- tabwid (/ tabht 2.0))) 0.0 0.0))) (setq mp (mapcar '* (mapcar '+ pt7 pt8) '(0.5 0.5))) (command "pline" pt5 pt7 "a" pt7 "CE" mp pt8 "L" pt6 "") (setq pt5 (mapcar '+ pt3 (list 0.0 (- tabedge) 0.0))) (setq pt6 (mapcar '+ pt3 (list 0.0 (- (+ tabedge tabwid)) 0.0))) (command "Break" ent1 pt5 pt6 ) (setq pt7 (mapcar '+ pt5 (list (- tabwid (/ tabht 2.0)) 0.0 0.0))) (setq pt8 (mapcar '+ pt6 (list (- tabwid (/ tabht 2.0)) 0.0 0.0))) (setq mp (mapcar '* (mapcar '+ pt7 pt8) '(0.5 0.5))) (command "pline" pt6 pt8 "a" pt8 "CE" mp pt7 "L" pt5 "") (setq pt5 (mapcar '+ pt2 (list 0.0 tabedge 0.0))) (setq pt6 (mapcar '+ pt2 (list 0.0 (+ tabedge tabwid) 0.0))) (command "Break" ent1 pt5 pt6 ) (setq pt7 (mapcar '+ pt5 (list (- tabwid (/ tabht 2.0)) 0.0 0.0))) (setq pt8 (mapcar '+ pt6 (list (- tabwid (/ tabht 2.0)) 0.0 0.0))) (setq mp (mapcar '* (mapcar '+ pt7 pt8) '(0.5 0.5))) (command "pline" pt5 pt7 "a" pt7 "CE" mp pt8 "L" pt6 "") (setq topr (mapcar '+ pt3 (list (+ tabwid 1.0) 1.0 0.0))) (setq botl (mapcar '+ pt1 (list (- (+ tabwid 1.0)) -1.0 0.0))) (command "join" "w" topr botl "") (setvar 'osmode oldsnap) (princ) ) (c:wow) Multi GETVALS.lsp

Description: I have a sample drawing where: The outer boundary is in red color (closed polyline). Inside this boundary, there are several cross polylines (in white). Some of these inside polylines are offsets or overlapping. My Requirement: I want to keep only the outermost polyline inside the boundary. The inner offset/cross polylines should be trimmed or deleted automatically. The result should leave only the clean outer boundary and remove the unwanted inner lines. Sample.dwg

"PI" is a valid lisp reserved variable so no need to work out all the angle values as decimal values. 0=0 90= (/ pi 2.) = 1.5707963267949 180= pi 270 = (* 1.5 pi) 45 = (* pi 0.25) and so on, in code where lots of hor and ver angles are used can just pre-set angles eg (setq a90 (/ pi 2.))

If all the objects touch ie no gaps, then this method should work, you draw a random closed pline around your objects, use BPOLY pick a point inside this dummy outer pline, two new plines will be made, erase the dummy and the new pline at the outer, you should now have a new pline wrapped around your objects.