Lisp Routine for Creating a Chamfer Line of Fixed Length

[Yasir.Aman]

I searched the forums but couldn't find an existing solution.

I'm looking for a Lisp routine that creates a chamfer line of a fixed length, provided by the user. The routine should calculate the distances for Distance 1 and Distance 2 (which are usually user-defined in AutoCAD's built-in chamfer command).

In my case, both distances for Line 1 and Line 2 will be equal. The angle between Line 1 and Line 2 can be anything greater than 0 and less than 180 degrees.

Please refer to the attached image for further clarification.

Thank you all!

[Kent1Cooper]

---

@komondormrex wrote:

this is holy everything but the autolisp, visual lisp and general customization imo.

---

[I'm not quite sure what you mean by that, but customizations other than by AutoLisp/Visual Lisp certainly have a place here, such as command macros and custom Hatch patterns and Linetypes.  I would categorize Python code as "general customization" as much as those.]

[komondormrex]

---

@Kent1Cooper wrote:

a first try.

---

i think first should always come first.

[komondormrex]

---

@Kent1Cooper wrote:

---

I would categorize Python code as "general customization" as much as those.]

---

can't find anything regarding python in the official autocad help. meant just this. anyway i think a python add-in is a cool feature, but...

[daniel_cadext]

Thank you for your interest in Python. Your right, it’s a community effort to create a better scripting language for AutoCAD. I’ve been wrapping ObjectARX and my daughter wrapped the ActiveX stuff. Since the project has started, others have contributed as well. It’s all open source. The intent is to serve the community

I’m not insensitive to your opinion. I only post when AutoLISP struggles to achieve a desired result, or to illustrate a concept that is language agnostic.

Cheers:)

~Dan

[Sea-Haven]

In built, no compilers required are Lisp and VBA. If Autodesk decide to include the Python core then it could become a 3rd open code. But the Autodesk push seems to be go down the developers path with Visual Studio. Lisp, .Net or C# etc. This may be a link with Microsoft. 

Look at Opendcl an improved version of dcl again a run time must be loaded. 

Personally I stay away from loading run time packages. I have enough problems with clients just using code provided without adding an overhead of making sure a runtime is loaded. A lot of clients have IT managers and would not allow adding run time packages. Where I use to work often downloaded stuff would fail and had to wait for IT to do their due diligence before we could use.

[daniel_cadext]

Hi,

- “In built”

Certainly, that has value. AutoLISP has been the go-to scripting language for the past two decades. Nothing to install, it’s just there.

- “no compilers required are Lisp and VBA”

Same with Python, you can write your code in notepad, of course and IDE with Autocomplete would make more sense.

- “Look at Opendcl”

A wonderful project to bring an amazing GUI interface to the community. OpenDCL team has done an amazing job. It’s open source, so it’s very low risk

- “Personally I stay away from loading run time packages”

Valid reasons for that, I remember times where I couldn’t get the current ObjectDCL or DOS_LIB libraries. But now they’re all open source.

The downside of not using runtime packages is, you can only offer your clients 25-year-old technology.

Myself, I demand more. I want to be able to extract attributes / other drawing data and hand it off to the latest and greatest data science / machine learning tools to produce estimations, material takeoffs, or what over data I need analyzed. Literally, thousands upon thousands of amazing packages, covering a huge range of industries available. Meanwhile, Lispers are still trying to connect to excel with ActiveX automation, not that there’s anything wrong with that, but it’s like trying to drive an F250 with a toilet bowl plunger as the gearshift.

- If Autodesk decide to include the Python core…

IMHO, it’s more likely than not. One of Autodesk’s competitors has just published Python wrappers for their ARX like API. It’s not open source, so your stuck with the company's release cycle

Every highschooler from here to Timbuctoo is learning Python and machine learning. If I’m a company, why would I train users to learn a 25-year-old scripting language that is basically cutoff from the outside world?  Point being, I think companies will demand it.

***Sorry, the thread has gone way off topic, please create a new one if you wish to continue the python discussion

[komondormrex]

i'm on the way

 

[Yasir.Aman]

@komondormrex. Wow! This looks amazing 😍.

Can't wait to see the final result. Fingers crossed.

Do you plan to include curves similar to @daniel_cadext 's algorithm?

[Yasir.Aman]

---

@daniel_cadext wrote:

***Sorry, the thread has gone way off topic, please create a new one if you wish to continue the python discussion

---

A thread on the topic would be interesting certainly.

[komondormrex]

surely i do

 

[Yasir.Aman]

Wow! I am getting excited so see the final product.

Will we be able to select a portion of polyline (e.g. one or more vertices) to be chamfered instead of the whole polyline?

[komondormrex]

yep

[Yasir.Aman]

@komondormrexThis feels like a dream come true. When can we expect to see the final product?

[komondormrex]

asap

[komondormrex]

---

@john.uhden wrote:

This would be a simple way (so long as the legs are treated as straight chords, not arc lengths)...

 that is exactly how they did it in the chamfer command)

[Yasir.Aman]

Thank you, @komondormrex!

This visual does an excellent job of illustrating how and why curves shift when using AutoCAD's built-in chamfer command.

[komondormrex]

@Yasir.Aman,

that is what i came up with for now. sort of a lengthy one, hence the fas.