yang686526

problems after entity has been marked for erase!
problems after entity has been marked for erase!
hi! all
i抳e have successfully erased entities from my imported dxf-drawings for quite a while now using below function. i can do a number of different operations both before and after i have marked one or several entities for deletion, no problems. i can save my dxf and everything is just fine.
the problem occurs when i抳e used the below delete function and i抦 to add some xdata to one or more of the remaining entities. i get a:
quote:
揢nhandled exception at 0x7c812aeb in singledoc.exe: microsoft c++ exception: oderror at memory location 0x0012f1c4..?
i抳e tried to use try ?catch blocks to narrow it down but with no success. i抳e looked in 揙pen design alliance forum?and also looked at the 揂llexamples?so far i haven抰 found anything that have been of any help to me (still looking).
however, if i comment out the following line then i can add xdata to my entities without any problems.
// pent->erase();
or if i set it to
// pent->erase( false );
my guess here is that i need to close down the pent after my erase-operation but so fare nothing have worked.
code:
////////////////////////////////////////////////////////////////////////
//description :
// delete all entity/entities.
//
void centity_utils::dodeleteentities()
{
try
{
odalayergetkeyactivities podalayergetkeyactivities;
oddbentityptr pent;
if( podalayergetkeyactivities.checkmessagebox_delete( _t("delete entities? ") ) )
{
oddbblocktableptr pblocks = api_fcc_get_document()->m_pdb->getblocktableid().safeopenobject();
oddbsymboltableiteratorptr pblkiter = pblocks->newiterator();
for (pblkiter->start(); ! pblkiter->done(); pblkiter->step())
{
// open the block
oddbblocktablerecordptr pblock = pblkiter->getrecordid().safeopenobject();
// get an entity iterator
oddbobjectiteratorptr pentiter = pblock->newiterator();
// for each entity in the block
for (; !pentiter->done(); pentiter->step())
{
oddbobjectid id = pentiter->objectid();
pent = id.safeopenobject(oddb::kforwrite);
if( ::api_fcc_get_view()->m_sset.contains( id ) )
{
//mark for erase
try
{
pent->erase();
}
catch(const oderror& e)
{
afxmessagebox( _t("when erase-flag is set: ") + e.description() );
}
}
}
}
//empty arrays, zoom extent, update!
::api_fcc_get_view()->m_sset_ctrl.clear();
::api_fcc_get_view()->m_sset.clear();
::api_fcc_get_view()->onzoomextent();
api_fcc_update_view();
}
else
{
//deselect
for(int i = 0; i < (int)::api_fcc_get_view()->m_sset_ctrl.length(); i++)
{
oddbobjectid id = ::api_fcc_get_view()->m_sset_ctrl.getat(i);
pent = id.safeopenobject(oddb::kforwrite);
pent->highlight( false );
}
}
}
catch(const oderror& e)
{
afxmessagebox( _t("overall: ") + e.description() );
}
}thanks! and a happy new year!
kennet
problems after...
it seems as if i've been barking up the wrong tree! not the first time i'm sorry to say.
after more then one day of digging i've finally come up with the fact that one of my arrays wasn't refreshed when it should have been. can't believe i've overlooked it, sorry folks!
best to all of you!
kennet