Base44
Mini tools
Jessye Ford's tools
-
```lisp ;*************************************************************************** ;* * ;* AutoCAD LISP - Thiแบฟt kแบฟ ngรดi nhร tแปฑ ฤแปng * ;* * ;*************************************************************************** ; Khai bรกo cรกc biแบฟn vร hแบฑng sแป (setq ;; Kรญch thฦฐแปc phรฒng (m) phong-chieu-dai 5.0 phong-chieu-rong 4.0 ;; Vแป trรญ phรฒng trong mแบทt bแบฑng phong-vi-tri-x 0.0 phong-vi-tri-y 0.0 ;; Kรญch thฦฐแปc thiแบฟt bแป vแป sinh (m) thiet-bi-ve-sinh-chieu-dai 1.5 thiet-bi-ve-sinh-chieu-rong 1.0 ;; Kรญch thฦฐแปc giฦฐแปng ngแปง (m) giuong-ngu-chieu-dai 2.0 giuong-ngu-chieu-rong 1.5 ;; Kรญch thฦฐแปc bร n ghแบฟ (m) ban-ghe-chieu-dai 1.0 ban-ghe-chieu-rong 0.5 ) ; Hร m tแบกo hรฌnh chแปฏ nhแบญt (defun tao-hinh-chu-nhat (x y chieu-dai chieu-rong) (command "RECTANGLE" (list x y) (list (+ x chieu-dai) (+ y chieu-rong))) ; Hร m tแบกo thiแบฟt bแป vแป sinh (defun tao-thiet-bi-ve-sinh (x y) (command "RECTANGLE" (list x y) (list (+ x thiet-bi-ve-sinh-chieu-dai) (+ y thiet-bi-ve-sinh-chieu-rong)))) ; Hร m tแบกo giฦฐแปng ngแปง (defun tao-giuong-ngu (x y) (command "RECTANGLE" (list x y) (list (+ x giuong-ngu-chieu-dai) (+ y giuong-ngu-chieu-rong)))) ; Hร m tแบกo bร n ghแบฟ (defun tao-ban-ghe (x y) (command "RECTANGLE" (list x y) (list (+ x ban-ghe-chieu-dai) (+ y ban-ghe-chieu-rong)))) ; Tแบกo phรฒng (defun tao-phong (x y) (command "LAYER" "M" "Phong" "" "" "") (setq ent (tao-hinh-chu-nhat x y phong-chieu-dai phong-chieu-rong)) (command "LAYER" "S" "Phong" "") ; Tแบกo thiแบฟt bแป vแป sinh (command "LAYER" "M" "ThietBiVeSinh" "" "" "") (tao-thiet-bi-ve-sinh (+ x 0.5) (+ y 0.5)) (command "LAYER" "S" "ThietBiVeSinh" "") ; Tแบกo giฦฐแปng ngแปง (command "LAYER" "M" "GiuongNgu" "" "" "") (tao-giuong-ngu (+ x 1.0) (+ y 1.0)) (command "LAYER" "S" "GiuongNgu" "") ; Tแบกo bร n ghแบฟ (command "LAYER" "M" "BanGhe" "" "" "") (tao-ban-ghe (+ x 2.5) (+ y 1.5)) (command "LAYER" "S" "BanGhe" "") ) ; Gแปi hร m tแบกo phรฒng (tao-phong phong-vi-tri-x phong-vi-tri-y) ;*************************************************************************** ;* * ;* End of LISP code * ;* * ;*************************************************************************** ```Jessye Ford๐ ๏ธ 1 tool ๐ 702 karmaOct 20, 2025@AutoCAD LISP Generator (JET-X)I apologize, but I'm not sure what you are referring to.
Comments
On AutoCAD LISP Generator (JET-X)
Jessye Ford
๐ ๏ธ 1 tool
๐ 702 karma
Oct 20, 2025
@AutoCAD LISP Generator (JET-X)
I apologize, but I'm not sure what you are referring to.
On Autocad assistance
Jessye Ford
๐ ๏ธ 1 tool
๐ 702 karma
Dec 18, 2024
i've asked my AI for assistance, I recieved a reply asking for clarification on a few things, and i responded with the additional details. I haven't gotten a reply and it has been over an hour or so since i replied. am i missing something?
On AutoCAD LISP Generator (JET-X) generation
Jessye Ford
๐ ๏ธ 1 tool
๐ 702 karma
Dec 18, 2024
I guess i should go a little further in to detail as to what my ultimate goal is. I am "automating" my companies fabrication dwgs so that the CAD operator would essentially only have to input data into the table cells and then all info and BOM and dimensions will be driven from the input. So that essentially if the QC person checks the data table, and verifies the info is correct, then there would not be as much time spent on checking the dwgs, effectively cutting cost drastically in that area. a set of dwgs can take anywhere from 6-8 hrs to complete per structure just to draw. then add another 5-6 hrs for checking and revisions, and the wasted money stackes up. my idea will cut the 12-15 hr process of completing dwgs down to MAYBE 2-3 hrs from start to finish. having said all that, I do not want the drafter to have to "manipulate" anything within the dwgs other than the data input. 1. I am comfortable with either dynamic blocks or LISP. Although I'm not fluent by any means in writing it, I can somewhat manipulate it to achieve most things. I would be interested in exploring both options at some point. 2. the text would need to change per dwg session. I'm using the slotted text to denote mk. no's for the fab shop. and the text displayed will be fields so it would need to update with the normal fieldeval or regenall options. 3. the dynamic block visibility states are driven by a custom LISP code that I compiled over the last few years. I will have potentially dozens of these objects per dynamic block and they will be incorporated into the visibility state that is needed. the only real "performance" consideration that i can think of at this time is for the slot to maintain its offset distance from the text, be annotative so that it scales properly, and for the slot to be able to stretch in relation to the insertion point. as there is ofter going to be other text or dwg elements within the vicinity that i do not want to obstruct or have to move each time. for instance, if it has an insertion point located on the left side, it would need to act as an "anchor" and the additional characters extent away from it, or contract towards it based on the number of characters in the field. and equidistant from the geometric center of the slot for text/slot that is center justified,regardless of which method we use those characteristics are a constant.
On AutoCAD LISP Generator (JET-X) generation
Jessye Ford
๐ ๏ธ 1 tool
๐ 702 karma
Dec 18, 2024
did i clarify or muddy the situation?
On AutoCAD LISP Generator (JET-X) generation
Jessye Ford
๐ ๏ธ 1 tool
๐ 702 karma
Dec 18, 2024
I guess i should go a little further in to detail as to what my ultimate goal is. I am "automating" my companies fabrication dwgs so that the CAD operator would essentially only have to input data into the table cells and then all info and BOM and dimensions will be driven from the input. So that essentially if the QC person checks the data table, and verifies the info is correct, then there would not be as much time spent on checking the dwgs, effectively cutting cost drastically in that area. a set of dwgs can take anywhere from 6-8 hrs to complete per structure just to draw. then add another 5-6 hrs for checking and revisions, and the wasted money stackes up. my idea will cut the 12-15 hr process of completing dwgs down to MAYBE 2-3 hrs from start to finish. having said all that, I do not want the drafter to have to "manipulate" anything within the dwgs other than the data input.
1. I am comfortable with either dynamic blocks or LISP. Although I'm not fluent by any means in writing it, I can somewhat manipulate it to achieve most things. I would be interested in exploring both options at some point.
2. the text would need to change per dwg session. I'm using the slotted text to denote mk. no's for the fab shop. and the text displayed will be fields so it would need to update with the normal fieldeval or regenall options.
3. the dynamic block visibility states are driven by a custom LISP code that I compiled over the last few years. I will have potentially dozens of these objects per dynamic block and they will be incorporated into the visibility state that is needed. the only real "performance" consideration that i can think of at this time is for the slot to maintain its offset distance from the text, be annotative so that it scales properly, and for the slot to be able to stretch in relation to the insertion point. as there is ofter going to be other text or dwg elements within the vicinity that i do not want to obstruct or have to move each time. for instance, if it has an insertion point located on the left side, it would need to act as an "anchor" and the additional characters extent away from it, or contract towards it based on the number of characters in the field. and equidistant from the geometric center of the slot for text/slot that is center justified,regardless of which method we use those characteristics are a constant.
