Named Object In NOD - Disappears?

[Kyudos]

I'm adding a named object to the root NOD. ArxDbg confirms it is there after I create it. But when I save the file and reopen it, the object is no longer in the NOD. Where did it go?

[Alexander.Rivilis]

This object is a custom object?

[Kyudos]

Yes, I thought I might have to use hard pointers in the NOD, but that doesn't help either.

[Kyudos]

ArxDbg further shows my object being erased when I save the file. What would cause that?

[Kyudos]

Hmmmm.... I fixed this by adding a subErase to my object, and vetoing attempts to remove it. Why would I have to do this? Is it because I'm putting it in the NOD root, not in 'my' dictionary?

[artc2]

There's nothing in AutoCAD that will automatically erase a generic object added to the NOD. But, if you are adding the object after a certain point in a save operation (i.e. after the handseed value has already been written to the dwg file), that can cause problems.

Another possibility would be if your object does decompose for save which could result in it being erased as part of being replaced by something else. But, if that were the case, I think you'd know about it.

[Kyudos]

Thanks  - I'm storing some 'last saved' information in my object, which I set in EditorReactor::beginSave.  Is that too late? If so, where can I set it?

[artc2]

Are you adding the object to the NOD in beginSave, or is it already added and you are are just changing its data?

[Kyudos]

I create the object in the dictionary when I initialise my document. I'm doing a getAt / change data / setAt in beginSave.

[artc2]

That shouldn't be a problem at all.

If you set up Visual Studio to use our symbol server you might be able to get call stack information that could help see what is doing the erase on save. The symbol server is http://symbols.autodesk.com/symbols

[Kyudos]

Unfortunately, I get nothing:

Just:

Object::SubErase

[External Code]

EditorReactor::beginSave

[External Code]

[artc2]

Are you running mixed for debug so that you can see the native as well as managed?

[Kyudos]

We aren't using any managed code - just C++.

[artc2]

Ok, then what is the version number of the AutoCAD you are using (so I can check to see if its symbols are on the symbol server)? This would be the value reported by the "_VERNUM" command or shown in the about box as the product version.

[Kyudos]

It is:

Command: _VERNUM
_VERNUM = "Q.104.0.0 (UNICODE)" (read only)

Or AutoCAD 2020.1.2

[autodaug]

Those names "Object" and "SubErase" in your stack suggest that there is managed code involved, somehow.  So it would be worth enabling managed debugging, just temporarily, to try to get more stack info.

I think your version of acad's symbols should be available on the server.  Here's an old post on how to get the symbols from the AutoCAD symbol server, which should still be fairly accurate.

https://through-the-interface.typepad.com/through_the_interface/2011/06/public-symbols-for-autocad-2...

There are a lot of symbols, and msdev has to search for them on the server via your network link. So if it is taking too long, you could change msdev to *not* automatically load *all* symbols.  And then explicitly tell it which modules' symbols to load, such as acdb24.dll and whatever other dlls you see on the stack.

[moogalm]

Hi,

It appears that symbols for AutoCAD Q.104 is not updated in our upstream servers.

I will have raise a request.

symchk "C:\Program Files\Autodesk\AutoCAD 2020\acdb23.dll" /s srv*C:\symbols*https://symbols.autodesk.com/symbols

SYMCHK: acdb23.dll           FAILED  - acdb23.pdb mismatched or not found

SYMCHK: FAILED files = 1
SYMCHK: PASSED + IGNORED files = 0

[moogalm]

Hi,

We have update debug symbols on our upstream servers https://symbols.autodesk.com/symbols

[autodaug]

Great, thanks for seeing to that!

It's still a mystery why the object is being erased during a beginSave notification.  Hopefully more stack info will show us who is erasing it.  Maybe a rogue beginSave handler is doing something unintended..

[Kyudos]

OK with the symbols I get:

acdb23.dll!AcDbImpObject::erase()	Unknown
acdb23.dll!eraseEntryObject()	Unknown
acdb23.dll!AcDbImpDictionary::setAt()	Unknown
acdb23.dll!AcDbDictionary::setAt(wchar_t const *,class AcDbObject *,class AcDbObjectId &)	Unknown
My.arx!My_EditorReactor::beginSave(AcDbDatabase * pDwg, const wchar_t * pIntendedName)

The erase is called by my call to setAt. Have I misunderstood how to change dictionary objects?

In My_EditorReactor::beginSave I have:

if (pDwg->getNamedObjectsDictionary(pNamedobj, AcDb::kForWrite) == Acad::eOk)
{
    MyObj* pObj = NULL;
    es = pNamedobj->getAt(_T("My_Obj"), (AcDbObject*&)pObj, AcDb::kForWrite);
    if (pObj != NULL)
    {
        pObj->SetInfo(....etc....);
        es = pNamedobj->setAt(_T("My_Obj"), pObj, DictId);
        es = pFp->close();
    }

Is the setAt not necessary?