Topic: Entmake after layer creation throws exception!

[zoltan]

This is driving me nuts!  I create a line with EntMakeX and in the DXF list I have a routine that checks if a layer exists.  If not it creates the layer and assignes it the color specified.
like this.

(EntMakeX (List '(0 . "LINE") (Cons 8 (CheckLayerName "Maintained" ) '(10 0.0 0.0 0.0) '(11 0.0 0.0 0.0)))

The layer is created correctly and the color is set, but when it gets back to the EntMakeX, it thows an exception:
; error: Exception occurred: 0xC0000005 (Access Violation)
; warning: unwind skipped on exception
; error: Exception occurred: 0xC0000005 (Access Violation)

when you try to save the drawing, AutoCAD crashes with a CER.

This is AutoCAD 2006

I have attached the file, let me know if you guy get the same result.

[Jeff_M]

Nope....

Command: crashme
<Entity name: 7ef7df10>

Worked first time/everytime.....although this isn't Vanilla Acad. This was tested with the "Land Enabled Map" option of Land Desktop 2006, SP1.

[Kerry]

Why are you defining the line with zero length ?

I seems to work as expected if there is a differential between start and endpoints.

[Kerry]

..and yes, in AC2006 the posted code spits the dummy

; error: Exception occurred: 0xC0000005 (Access Violation)
; warning: unwind skipped on exception
; error: Exception occurred: 0xC0000005 (Access Violation)
; error: Exception occurred: 0xC0000005 (Access Violation)
; error: Exception occurred: 0xC0000005 (Access Violation)
; error: Exception occurred: 0xC0000005 (Access Violation)
_$

.. continuable sometimes ..
then FATAL ERROR if save attempted

[Glenn R]

It's most likely crashing because you haven't assigned an owner to the newly created object - then when it goes to save...BOOM!
EntMakeX creates an entity, but it DOES NOT assign an owner to that entity. Try using EntMake instead.

Cheers,
Glenn.

[Kerry]

DUH ! I Couldn't see the forest for the trees ..

[Glenn R]

That twice in less than a week Kerry 

Merry Xmas,
Glenn.

[Kerry]

 


Seasons Greeting to you too Glenn

Be Well
Kerry

[zoltan]

I am defining a line with 0 length because I will be moving the endpoints later with EntMod.  Making them different still crashes for me.  Also I need the ENAME so I don't want to use EntMake, beside it still crashes.  I just installed Service Pack 1a for Mechanical Desktop and it still crashes.  I have Inventor Series 10 loaded.

Glenn, please explain to me this idea of assigning an owner to an object after making it, because that is new to me.

[Kerry]

Just change the EntMakeX to EntMake.

[SMadsen]

Zoltan, if the only thing you want is to have an ename returned you should be able to grab it after using ENTMAKE. For built-in functions that mess with the drawing database, it's far more important what the function does than what it returns.

A simple inline example of grabbing the ename could be:

Code: [Select]

(cond ((entmake (list '(0 . "LINE")
                      (cons 8 (CheckLayerName "Maintained" 8))
                      '(10 0.0 0.0 0.0)
                      '(11 20.0 10.0 0.0)
                )
       )
       (setq ename (entlast))
      )
)

[zoltan]

Using Entmake instead of EntmakeX still causes an exception for me.

 So what is the difference between EntMake and EntMakeX.  I always thaught that the first returns the EData and the latter returns the EName.  So what is this stuff about assigning an owner? How do you do thais in Lisp?

[LE]

I do not have A2006.

What happens if you use visual lisp activex function instead of entmake ?

[zoltan]

Ok, I figured out this stuff about owning objects.

When I use VLA-AddLine, it thows and exception and crashes imediatelly with a CER

[zoltan]

ok, Sorry, VLA-AddLine works, I just did'nt change it for all of them.

That is the way it will have to be then.

[LE]

ok, Sorry, VLA-AddLine works, I just did'nt change it for all of them.

That is the way it will have to be then.

Also, test this:

Code: [Select]

(Defun C:CrashMe  ()
  (CheckLayerName "Maintained" 8)
  (vla-update zf_Acad-Object)
  (EntMakeX
    (List '(0 . "LINE")
  (cons 8 "Maintained")
;;;   (Cons 8 (CheckLayerName "Maintained" 8))
  '(10 0.0 0.0 0.0)
  '(11 0.0 0.0 0.0)))
  )

Must work, I tested your code and was crashing also on autocad 2005, and even tried with my own functions following the same steps as yours and the same crashing, until I took out the layer definition and by forcing an update to the acad object.

[zoltan]

Now THAT makes sense!  Thanks LE.  Also should I clear the value of zf_Acad-Object so (ZF_Get-Acad-Object) gets a new instance, or is the pointer the same after the object is updated?

[LE]

Now THAT makes sense!  Thanks LE.  Also should I clear the value of zf_Acad-Object so (ZF_Get-Acad-Object) gets a new instance, or is the pointer the same after the object is updated?

I followed your code.... I normally used to simple make a call of:

Code: [Select]

(vlax-get-acad-object)

Anytime I needed and never got any problems.

I also every time I access an activeX automation server via getinterfaceobject or xxx-create-object, I make a call to release and gc...

Have fun.

[zoltan]

Don't you find it tedious to get a reference to the Acad-Object, the ActiveDocument, and Modelspace every time you want to creat an entity?  I use the ZF_Get-* functions to save alot of typing.  It caches the object in a variable that it can return instead of getting a new reference every time.  It's faster and I've never had a problem...until now.

Concerning releasing the object after the GetInterfaceObject: that is a good point.  I always made a habit of it when getinng an instance of Excel of other APIs, but I kinda forgot that AutoCAD.AcCmColor.16 is another API.  I guess I should write a subroutine that releases the color object stored in zf_AcadColor and set it to nil, so the next call to (ZF_Get-AcadColor) has to get a new instance every time.

it would look like this:

Code: [Select]


(VLA-Put-TrueColor oEntity (GetColor iColor))
(ReleaseColor)


It might be a good idea to wait on releasing the color untill the end of processing alot of entities, since getting an interface object if kinda slow.  What do you folks think?


good stuff, I learned alot today.

[LE]

Don't you find it tedious to get a reference to the Acad-Object, the ActiveDocument, and Modelspace every time you want to creat an entity?  I use the ZF_Get-* functions to save alot of typing.  It caches the object in a variable that it can return instead of getting a new reference every time.  It's faster and I've never had a problem...until now.

I was referring to only make a call to (vlax-get-acad-object) instead of having a global, for the other ones you mentioned is what I normally do.