All Activity

Nice one Bigal, Thank you!

Not sure if this is useful it tracks all commands used in a session Productivity_Analysis_Tool.lsp

Not sure if the lisp by YMG will read 3dfaces. CIV3d will do it same with other civil packages like Civil Site Design.TriangV0.6.7.LSP

The probable answer is CVPORT but how are you making the animation ? You can in a lisp change layouts and viewports use the DELAY command to slow down the changing between layouts etc.

If this is Road pavement volumes then may need CIV3D or Civil Site Design which have volume reports which include volume & area between chainages.

There are no commands - just load it, use a few LISP commands, and then save your drawing.

Yes I suppose if the log is to be maintained continuously, existing content could be parsed and updated accordingly - if more than just the OP are using this code, I'll look to update it.

I don't understand, if your just picking two points why are you not just doing (command "_.BREAK" "0,0.3" "0,-0.3")

Thank you Tsuky, works exactly as i needed.

Hi, With your drawing, this code will correct the polylines. To be adapted if used in another drawing (ssget filter) (vl-load-com) (defun c:Correct3DPL ( / ss AcDoc Space nb n ename obj l_pt lay new_obj) (setq ss (ssget "_X" '((0 . "POLYLINE") (67 . 0) (8 . "CTL_PNT") (66 . 1) (70 . 9)))) (cond (ss (setq AcDoc (vla-get-ActiveDocument (vlax-get-acad-object)) Space (if (= 1 (getvar "CVPORT")) (vla-get-PaperSpace AcDoc) (vla-get-ModelSpace AcDoc) ) nb 0 ) (repeat (setq n (sslength ss)) (setq ename (ssname ss (setq n (1- n))) obj (vlax-ename->vla-object ename) l_pt (vlax-get obj 'Coordinates) lay (vlax-get obj 'Layer) ) (cond ((eq (length l_pt) 12) (vla-delete obj) (setq new_obj (vlax-invoke Space 'Add3dPoly (cdddr l_pt))) (vla-put-Closed new_obj :vlax-true) (vla-put-Layer new_obj lay) (setq nb (1+ nb)) ) ) ) (princ (strcat "\n" (itoa nb) " polylines corrected.")) ) ) (prin1) )

Lee it is a rare day when I find an improvement for you, and it might be today... might be... In your onsave would it be preferable to take any strings that 'sel' finds in the ssget and append the new commands to them? Maybe put some sort of delimitator between old and new strings? Reason I ask, it is not unusual for me to complete a drawing over a few sessions - end of day into the next day being most common - which means the reactors will be reset... but the commands used will still need to be listed.

Yes, I may have opened the same drawing several times. I noticed that if I use 2 lisps, then close the file, but cancel closing it and continue working in this file with new codes, when I close it again, the suggestion to save the list of commands does not appear...

not in this case , unless i am doing something wrong. I have attached example dwg. Basically i had 3DFaces as Triangles and converted them using lisp into 3dpolyline Triangles, but it creates 4 Vertices for each Triangle, another lisp which supposed to create contours over triangles refusing to do so and say 3dpolylines are not closed polylines. sample.dwg

Please explain how to use it correctly, which command to call?

Thanks @GLAVCVS I would advise against (vlr-remove-all), as this will remove all reactors defined within the session, not only those defined by your program.

Great code, as always, Mr. Lee As for mine, I think I forgot that some reactors are persistent. So, Nikon, the problem is that you must have opened the same drawing several times in the same AutoCAD session, and several prompts have accumulated, repeating the request several times. That problem shouldn't occur anymore with this new code. Also, you'll be able to see the text inserted before confirming the closing of the drawing. Simply replace the "fota" function in your "acad2021Doc.lsp" with this new one. (defun fota (/ arch cad cmd mens) (defun pregunta (a b / cad) (cond ((= (car b) "CLOSE") (if (and *lstCmds* (setq mens (cmdsCargados)) (= (vlax-invoke-method (vlax-create-object "wscript.shell") 'popup "驴Dejar en el dibujo un MTEXT con todos los comandos utilizados?" 0 "Guardar comandos usados" 4) 6) ) (progn (vlr-remove-all) (vla-AddMText (vla-get-modelspace (vla-get-activedocument (vlax-get-acad-object))) (vlax-3d-point (getpoint "\nInsertion point...")) 100 mens) (vlax-invoke-method (vlax-get-acad-object) 'Update) ) (vlr-remove-all) ) ) ((= (type a) 'VLR-Lisp-Reactor) (if (not (member (setq cad (substr (car b) 4 (- (strlen (car b)) 4))) *lstCmds*)) (setq *lstCmds* (cons (substr (car b) 4 (- (strlen (car b)) 4)) *lstCmds*)) ) ) ) ) (vlr-remove-all) (foreach sim (atoms-family 0) (if (wcmatch (setq cmd (strcase (vl-princ-to-string sim) T)) "c:*") (setq *afI* (cons sim *afI*)) ) ) (setq *r* (vlr-command-reactor nil '((:vlr-commandwillStart . pregunta)))) (setq *r1* (vlr-lisp-reactor nil '((:vlr-lispwillstart . pregunta)))) )

Here's a quick & dirty version - it's not advisable to prompt the user for any input as part of a reactor callback. (defun init ( ) (foreach grp (vlr-reactors :vlr-command-reactor :vlr-lisp-reactor) (foreach rtr (cdr grp) (if (= "lisp-commands" (vlr-data rtr)) (vlr-remove rtr) ) ) ) (setq lisp-command-list nil) (vlr-command-reactor "lisp-commands" '((:vlr-commandwillstart . onsave))) (vlr-lisp-reactor "lisp-commands" '((:vlr-lispwillstart . onlisp))) (princ) ) (defun onsave ( rtr arg / idx lyr sel str ) (setq lyr "lisp-commands") (cond ( (not arg)) ( (not (wcmatch (setq arg (strcase (car arg))) "SAVE,QSAVE,SAVEAS"))) ( lisp-command-list (if (setq sel (ssget "_X" (list (cons 8 lyr)))) (repeat (setq idx (sslength sel)) (entdel (ssname sel (setq idx (1- idx)))) ) ) (setq str "") (foreach itm (vl-sort lisp-command-list '(lambda ( a b ) (> (cdr a) (cdr b)))) (setq str (strcat str "\\P" (car itm) "\t\t" (itoa (cdr itm)))) ) (makelayer lyr) (entmakex (list '(0 . "MTEXT") '(100 . "AcDbEntity") '(100 . "AcDbMText") '(010 0.0 0.0) (cons 1 (substr str 3)) (cons 8 lyr) ) ) ) ) (princ) ) (defun onlisp ( rtr arg / fun itm ) (cond ( (not arg)) ( (wcmatch (setq arg (strcase (car arg))) "~(C:*)")) ( (setq fun (substr arg 4 (- (strlen arg) 4)) itm (assoc fun lisp-command-list) ) (setq lisp-command-list (subst (cons (car itm) (1+ (cdr itm))) itm lisp-command-list)) ) ( (setq lisp-command-list (cons (cons fun 1) lisp-command-list))) ) (princ) ) (defun makelayer ( lay ) (if (not (tblobjname "layer" lay)) (entmake (list '(0 . "LAYER") '(100 . "AcDbSymbolTableRecord") '(100 . "AcDbLayerTableRecord") '(070 . 0) (cons 2 lay) '(062 . 8) '(290 . 0) ) ) ) ) (vl-load-com) (init)

I load programs and use them.

I need you to explain a little more. Did you use multiple Lisp commands or just load files? Take a screenshot of the code you pasted into the "acad2021Doc.lsp" file.

I tested the code a bit more, sometimes the window with the message "Display commands on the screen?" does not work correctly. I have to click "Yes" several times, I specify the insertion point of the text, but the window appears again, and if I click "No", the window also appears several times. And one more small note, when I specify the insertion point, I don't see how the text is inserted. A window about saving the drawing appears immediately… Maybe I'm doing something wrong...

Maybe this might help: Lee Macs option at the end might give you a start. Do you want it to open the viewports automatically or with the user perhaps pressing say 'space' bar?

Hello, good day. I’d like to continue working on the material volume tables in AutoCAD — specifically the ones that have been exploded and no longer retain a defined table structure. These tables begin with a top row that contains the stationing of each section, formatted like this: Material(s) at Station 0+250.00 This first row contains only one column. The second row has four fixed columns that serve as headers for the data rows below. These headers are consistent across all sections and do not change. From left to right, they are: Material Name Area Volume Cumulative Volume The third row and all subsequent rows contain the actual data, aligned with the headers above. The material names may vary from project to project, but within a single project, they remain consistent across all sections. In the second column of each row, the area of the material is listed as a numeric value. The third column contains the volume, and the fourth column contains the cumulative volume. Since these tables have been exploded, the numbers no longer update automatically. That’s why we need a solution where, after manually updating the area values, the corresponding volumes and cumulative volumes are automatically recalculated and replaced in the table. So far, all our attempts to achieve this have failed. Now I’d like to share some insights that might help: Stationing is critical. The first step must be to extract the station number from the top row as an integer. This allows us to calculate the distance between two consecutive sections, which is essential for computing the volume of a truncated cone. Area values should remain unchanged. We only need to read them and use them in calculations to update the Volume and Cumulative Volume columns. New observation about table geometry: The vertical spacing between the second row and all subsequent rows is exactly three times the text height. Also, the insertion point (X coordinate) of the area values is exactly aligned with the insertion point of the word “Area” — and the same applies to the Volume and Cumulative Volume values. Update logic: Let’s assume we have only one material row (though usually there are more). Let’s name the area value in the first section A1, and the area in the second section A2. These two values represent the top and bottom surfaces of a truncated cone with height H, where H is the difference between the station numbers of the two sections. The calculated volume should replace the volume value in the second section. Then, this volume should be added to the cumulative volume from the first section, and the result should replace the cumulative volume in the second section. Naturally, this volume and cumulative update must follow the correct station order

I need a lisp code to open named viewports one after another. To view as animation.

I'm not sure...

OVERKILL should remove the duplicate vertices.