Commandobill Posted June 16, 2009 Posted June 16, 2009 I was messing around with entmakex and attempting to make an mline (which i finally accomplished). But then when i selected said object a fatal error occured and autocad shutdown. I ran it a few times and this happend. Any idea why? Quote
Commandobill Posted June 16, 2009 Author Posted June 16, 2009 Nobody? Oh well here's a copy of the code i used... (entmakex '((0 . "MLINE") (100 . "AcDbEntity") (67 . 0) (8 . "0") (100 . "AcDbMline") (2 . "STANDARD") (40 . 1.0) (70 . 0) (71 . 1) (72 . 2) (73 . 2) (10 -1.74644 3.64127 0.0) (210 0.0 0.0 1.0) (11 -1.74644 3.64127 0.0) (12 0.999997 -0.0023447 0.0) (13 0.0023447 0.999997 0.0) (74 . 2) (41 . 0.0) (41 . 0.0) (75 . 0) (74 . 2) (41 . -1.0) (41 . 0.0) (75 . 0) (11 13.5136 3.60549 0.0) (12 0.999997 -0.0023447 0.0) (13 0.0023447 0.999997 0.0) (74 . 2) (41 . 0.0) (41 . 0.0) (75 . 0) (74 . 2) (41 . -1.0) (41 . 0.0) (75 . 0) ) ) Quote
Commandobill Posted June 16, 2009 Author Posted June 16, 2009 and whats really strange is i can 'ssget' select it with no problems... Quote
Lee Mac Posted June 16, 2009 Posted June 16, 2009 No Fatal Error for me when testing da code... Quote
Commandobill Posted June 16, 2009 Author Posted June 16, 2009 No Fatal Error for me when testing da code... Thanks. did you try selecting the mline it makes? Quote
The Buzzard Posted June 16, 2009 Posted June 16, 2009 Yeah, nothing out of the ordinary. I got this on the command prompt. ; error: Exception occurred: 0xC0000005 (Access Violation) ; warning: unwind skipped on exception ; error: Exception occurred: 0xC0000005 (Access Violation) Quote
TimSpangler Posted June 16, 2009 Posted June 16, 2009 Crashed for me as well. If I remember correctly (form the adesk forums) there was talk about not using entmake for mlines. Use vla-addmline instead. You might want to start there. Quote
Lee Mac Posted June 16, 2009 Posted June 16, 2009 Its weird how it worked on 2010 - maybe something they fixed at a later date... :wink: Quote
Commandobill Posted June 16, 2009 Author Posted June 16, 2009 Thank you everyone for your input. It seems I chose the wrong thing to mess with. Thanks again! Quote
The Buzzard Posted June 16, 2009 Posted June 16, 2009 Its weird how it worked on 2010 - maybe something they fixed at a later date... :wink: Lee, I think you are on to something. I first ran it 2004 and got the fatal error message. I just tested the same routine on 2009 and no problem. It drew the lines. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.