yang686526

odgicontextfordbdatabase::enablegsmodel
odgicontextfordbdatabase::enablegsmodel
hello,
i'm gratified with the fast drawing speed in the version 1.13.
by the way, after using enablegsmodel(true), a run-time error occured in creating device ( m_pgs->createdevice() ) after reloading.
if set enablegsmodel(false), it was ok.
so i consider that the un-release of the contents that have been cached cause the problem.
call stacks are as follows:
//
odgsmodelholder::~odgsmodelholder() line 26 + 16 bytes
odgslayouthelperimpl<odgsmodellayouthelper>::~odgs layouthelperimpl<odgsmodellayouthelper>() + 53 bytes
odgsmodellayouthelperimpl::~odgsmodellayouthelperi mpl() + 22 bytes
odrxobjectimpl<odgsmodellayouthelperimpl,odgsmodel layouthelperimpl>::~odrxobjectimpl<odgsmodellayout helperimpl,odgsmodellayouthelperimpl>() + 22 bytes
odrxobjectimpl<odgsmodellayouthelperimpl,odgsmodel layouthelperimpl>::`scalar deleting destructor'(unsigned int 1) + 22 bytes
odrxobjectimpl<odgsmodellayouthelperimpl,odgsmodel layouthelperimpl>::release() line 75 + 32 bytes
odsmartptr<odgsdevice>::release() line 217 + 19 bytes
odsmartptr<odgsdevice>::assign(const odgsdevice * 0x016ea9f0) line 80
odsmartptr<odgsdevice>erator=(const odsmartptr<odgsdevice> & {...}) line 238 + 46 bytes
csingledocview::resetdevice(unsigned char 1) line 126 + 57 bytes
csingledocview:ninitialupdate() line 120
//
please, give me your advice.
regards,
ktwinkle
last edited by ktwinkle; 22nd may 2005 at 11:42 pmfff">.
hi,
thanks for the report.
it's a bug in dd.
you can use the following workaround for now: destroy gs (csingledocview::m_pdevice.release()) before destroying db (csingledocapp::m_pdb.release()).
thanks for your reply.
once after vectorzing in a caching mode ( enablegsmodel( true ) ) , reloading and vectorizing other dwg file cause trouble at m_pdevice.release. (same call stacks as above).
when should insert the releases of gs and db?
or is there another solution?
the essential thing is to be able to load and vectorize several files repeatedlyfff"> using a caching mode in sdifff">.
as i understand you used singledoc example as a scratch for your mfc application. i reproduced bug in singledoc and redesigned it to walk aroung the bug. i modified singledoc and it works fine for me with dd 1.13. i faled to attach archive to this message. so please give me you e-mail i'll send it directly to you.
thanks for your help.
my e-mail address is "ktwinkle@3gcore.com".
could you please send me the example too?
quote:
originally posted by dmitry a. novikov
as i understand you used singledoc example as a scratch for your mfc application. i reproduced bug in singledoc and redesigned it to walk aroung the bug. i modified singledoc and it works fine for me with dd 1.13. i faled to attach archive to this message. so please give me you e-mail i'll send it directly to you.
hello, i have the same problems discussed in this thread. could you please send me your modified singledoc project. my email adress: "marckhoff@elias-gmbh.de"
thank you for your help.
here you are.
attached files (23.9 kb, 16 views)