TheSwamp
Code Red => AutoLISP (Vanilla / Visual) => Topic started by: Marc'Antonio Alessi on November 30, 2022, 12:59:45 PM
-
Open DWG > the ML is selectable…
Rigen Command: Regen > the ML NOT is selectable…
it also happens to change some settings of the layers
NOT happens if PDMODE is 0 or 1 :tickedoff:
-
Rigen? It works for me on 2023.
-
Same for me... Seems like its selectable and editable with the attribute.
-
Rigen? It works for me on 2023.
Sorry, Regen. Rigen is in Italian ...
-
Rigen? It works for me on 2023.
Sorry, Regen. Rigen is in Italian ...
I learned something new today :-)
-
AutoCAD 2023 need 2 command Regen
AutoCAD 2019 need 1 command Regen
AutoCAD 2013 need 1 command Regen
BricsCAD no problem
The Multileader IS always selectable by Point inside (X), if I move the ML by point inside it it becomes selectable again.
Sorry for my english :whistling:
-
Rigen? It works for me on 2023.
Sorry, Regen. Rigen is in Italian ...
I learned something new today :-)
Si, prova a guardare la GIF che ho inviato… :-)
-
I'd like to at least know if anyone had the same behavior :?
-
I see what you mean, if I regen, it’s hard to select, you can’t run (entget(car(entsel))) on the leader section either… only the X
-
If I drag it around by the X, the leader becomes select-able again..... but then it goes away once you regen again
-
even if I add arrows, the grips don't show... wondering how this was created?
-
even if I add arrows, the grips don't show... wondering how this was created?
it was done with AutoCAD commands... including the MultiLeader style… :knuppel2:
For the moment I have solved with PDMDE 0, I have to try if removing the POINT resolves it (out of curiosity, because I need the POINT)
Grazie :-)
-
even if I add arrows, the grips don't show... wondering how this was created?
it was done with AutoCAD commands... including the MultiLeader style… :knuppel2:
For the moment I have solved with PDMDE 0, I have to try if removing the POINT resolves it (out of curiosity, because I need the POINT)
Grazie :-)
I checked: it's the POINT inside the block that creates this problem :x :idiot2: :roll: