question about disableundorecording
question about disableundorecording
here a sample of my code (simplified):
testundorecording(oddbdatabaseptr &oddbptr, oddbobjectid odobjid)
{
oddbptr->startundorecord();
oddbptr->disableundorecording(true);
oddbobjectptr objptr = odobjid.safeopenobject(oddb:
penmode::kforwrite);
objptr->erase();
objptr.release();
oddbptr->disableundorecording(false);
objptr = odobjid.safeopenobject(oddb:
penmode::kforread, true);
}
this code doesn't work, i have an exception: "object was permanently erased", in the second safeopenobject.
is it the right thing to do to open an erased entity that wasn't undo recorded or is there a problem with disableundorecording ?
if undo recording is disabled erase() erased object permanently and it gets removed from memory. in such case the object can't be opened again.
compare:
code:
delete pmyobject;
pmyobject->dosomething();
sergey slezkin
maybe, but in objectarx it doesn't work like that.we can open an erased entity even if undo recording was disable when the entity has been erased.
we are adn developpers and we are looking for a solution to replace autocad.
dwgdirect is the solution, we are making our own cad application, for the moment i am just trying to see if our objectarx code using acdbobject can be replace by the same in dwgdirect with oddbobject.
now i just want to know if disableundorecording will definitively work like that or will you try to have the same as objectarx ?
objectarx code (who works):
void testdisableundorecording(acdbobjectid objid)
{
acdbentity *pent;
acdbcurdwg()->disableundorecording(adesk::ktrue);
if (acdbopenacdbentity(pent, objid, acdb::kforwrite) == acad::eok)
{
pent->erase();
pent->close();
}
acdbcurdwg()->disableundorecording(adesk::kfalse);
if (acdbopenacdbentity(pent, objid, acdb::kforread, adesk::ktrue) == acad::eok)
{
pent->close();
}
}
as i understand in objectarx erased objects always stay in memory (untill the drawing is saved and reloaded). or is where a method to free memory used by erased objects?
i think it's useful opportunity.
sergey slezkin
you are right and reloading a database is the only way to free memory used by erased objects (as i know).
as you say it's a usefull opportunity, will you integrate this behavior in dwgdirect ?
just a remark, in dwgdirect you have it. i mean that if i call neither startundorecord() nor disableundorecording(), i can erase an entity and reopen it.