All Activity

like i said its not really the avg per say because its missing data points. should probably use the larger/longer poly to pull points from (or maybe both and avg it out). The blue line is suffering from not enough detail since its only calculating off the vertex. i can't test right now but see if the selecting order changes anything. Also change the following and should get a better path. tho it will create a poly with 10x the vertex of selected one. (setq i (+ i 0.1))

Is this a dynamic block? If not, that might be the way to handle this situation.

Thanks again for your code, @mhupp It seems that the differences in the turning zones between the resulting geometry and the expected geometry persist. I must say that the goal is to obtain an axis that remains equidistant from the reference polylines at all times. I thought this problem would easily find a solution here. Maybe I was wrong

... I tried replacing 'objectdbx.axdbdocument' with 'GStarX.axdbdocument': it keeps giving me the error VLA-OBJECT #<%catch-all-apply-error%>

Then you need to upgrade or follow my recommendation on searching the web for workarounds. I gave you a start with two relevant links.

That's an Express Tool not available in AutoCAD LT. I was going to suggest the Excel Macro method. Maybe a Script can be used. Was an AutoCAD LT expert around here that did all kinds of customizations, including using Excel, before LT had AutoLISP function. @steven-g IIRC.

How can I modify this LISP routine to use millimeters instead? ;; CAB 05.12.09 ;; Draw Electric Wire (defun c:ew (/ ew_layer p1 p2 msg) (setq ew_layer "Wire") ; layer name (defun draw-ew (p4 p1 lay / p2 p3) (setq p2 (polar p1 (- (angle p1 p4) (/ pi ) 57.40259411) p3 (polar p4 (+ (angle p4 p1) (/ pi ) 57.40259411) ) (entmakex (list '(0 . "LWPOLYLINE") '(100 . "AcDbEntity") '(100 . "AcDbPolyline") (cons 8 lay) (cons 90 4) '(70 . 0) ; 1 for closed 0 overwise (cons 10 p1) '(40 . 0.0) '(41 . 0.0) '(42 . 0.198912) (cons 10 p2) '(40 . 0.0) '(41 . 0.0) '(42 . 0.0) (cons 10 p3) '(40 . 0.0) '(41 . 0.0) '(42 . 0.198913) (cons 10 p4) '(40 . 0.0) '(41 . 0.0) '(42 . 0.0) ) ) ) (setq p1 (getpoint "\nPick start point (Draw clockwise")) (setq msg "\nPick next point clockwise.") (while (setq p2 (getpoint p1 msg)) (draw-ew p1 p2 ew_layer) (setq p1 p2) ) (princ) ) (prompt "\nElectric Wire loaded, Enter EW to run.") (princ)

Tengo un lisp que pone grilla en un viewport, funciona bien, pero solo en viewport que no estan rotados, no se mucho de lisp, casi nada, pero buscando por aqui y alla, lo logre contruir. el caso es que ya no pude hacer que ponga la grilla si esta rotado, otra cosa es que si el viewport no es completamente rectangular o cuadrado, se sale del limite del viewport, aqui esta grilla v2.lsp

attout and attin?

Ok a few comments, Lets start, as mentioned when they added lisp to LT they decided to leave the smart stuff out, typical Autodesk, so you can not talk direct to Excel, Full Acad, or Bricscad, plus I believe a few others no problem. Just a side comment can also use Libre Calc. From Cad, yes can get range used," so get a list of all "A" column values no user input. Then find the one your looking for this will give you a row value. So put the attributes values into a cell. I have "Alan Excel.lsp" which is a lot of defuns that do different tasks I have saved the latest version in the download section. I have acknowledged those that have helped in putting it together the extra defuns, I keep adding to it depending on task. One thing you can do is check (setq xlApp (vlax-get-or-create-object "Excel.Application")) if it errors or returns NIL that would occur in LT. Please let me know. If its a simple nil then do the export to csv and use say (alert "Run the macro to import the csv file"), as a side note pretty sure in full version could call the macro, so one common code only. There is one little glitch when you need to go to Excel to do something user wise you must click on Excel window, but I did find a way around it using Powershell that is called from the CAD so it auto jumps to Excel. Should be able to do same in excel jump back to cad. Just google about your Excel macro questions there is huge amount of info out there use VBA answers and convert to Lisp sometimes.

HI, I'm running version 12, Regards, Lu

Hello The problem may be in ObjectDBX. Try replacing "objectdbx.axdbdocument" with "GStarX.axdbdocument"

The request for verification can be turned off with the BATTMAN command.

I checked: it works on Autocad... on GstarCAD it doesn't work. It doesn't matter, I use your previous file that reported the error but didn't allow renaming (CAPFD) thank you so much RLX for your effort!

Thanks a lot, @mhupp I'll try your code.

For completeness, the key here is the "Repeat" option of the -INSERT command - though, I'm unsure in which version this relatively new keyword was introduced.

Thank you very much eldon for your reply

As Lee says, it doesn't know, it is a bit of a blunt LISP that does the job and no more. Lees is much better but I had a mental block yesterday, couldn't remember cmdactive.

If you need more information, check the documentation on the CMDACTIVE system variable.

It won't - it will continue indefinitely until the user presses Esc to force it to exit.

I am still new with Lisp, but it feels that this is more elegant by checking if a command is active?

So the first line keeps doing the loop while it is not nil? How will it know it is not nil?

I think I've achieved a workaround. I'm going to set a macro within excel that exports the data to a CSV every time the excel document is saved (overwriting the existing versions). I'm then going to read this using the standard IO functions available to me in LT. It's not the cleanest solution, but I believe it should work. If anyone has any advice regarding pitfalls etc. that I might encounter please feel free to enlighten me

That's unfortunate @Steven P haha if only it were this simple...Honestly I've never experienced resistance like this before! Could a LISP in LT export the Excel data to a CSV, pull the data from that, and the delete the CSV? I'm going to assume that the answer is no due to the lack of vlax-get-or-create-object.

Yeah, LT is a problem, you won’t have vlax-get-or-create-object, you could probably parse .CSV files though