yang686526

exporting to dwf with low memory footprint
exporting to dwf with low memory footprint
hi,
i'm trying to export a dwg file to a dwf, while making a small as possible run time memory footprint.
when loading the dwg using a partial load, it works fine, up until exportdwf is called, which consumes all of the memory (as thus making the partial load ineffective).
i've tried using my custom-made page controller (same as the one used in odwriteex) - both kpage and kunload are used.
doesn't work, since one specific method causes all of the memory allocation: cdwfexportimpl::draw() -> which calls m_pdevicedwf->update();
the update method is a native dwgdirect library function, and while it's running i can't page any objects (and after it's done running, it's too late since too much memory is consumed already).
note: using meterprogress to page objects while exporting doesn't help here, since it's not being called while the native update method is running.
i've also tried to export only parts of the dwg:
removing some layers before exporting. doesn't work since this doesn't remove the entities within those layers.
removing some of the entities before exporting. doesn't work, since oddatabase->purge method iterates through all of the database's entities and consumes all of the memory.
my question is this:
is there any way to export to dwf without making a large memory footprint? can this be achieved by exporting only part of the dwg (and if so, how can it be done without consuming a lot of memory)?
thanks,
yaron
last edited by yaron.budowski@c4-security.com; 15th february 2009 at 09:37 amfff">.
you may attach database reactor and call paging from there (every 100 objects e.g.)
not sure if it will work, but it's worth trying.
vladimir
i checked my reactor idea, and it is not working - there is no notification called when the object is loaded from disk.
you may patch dwf export: overload regenabort() virtual function in oddwfdevice and call oddbpageobjects() there from time to time.
to build dwf export you will need autodesk dwf toolkit. it may be freely downloaded from their site.
unpack dwf toolkit to \thirdparty\dwftoolkit-7.3 directory
vladimir
quote:
originally posted by vkalinin
you may patch dwf export: overload regenabort() virtual function in oddwfdevice and call oddbpageobjects() there from time to time.
to build dwf export you will need autodesk dwf toolkit. it may be freely downloaded from their site.
unpack dwf toolkit to \thirdparty\dwftoolkit-7.3 directory
thanks for the reply - i've checked it out, and it seems that regenabort is called for the first time after most of the memory is already consumed.
last edited by yaron.budowski@c4-security.com; 17th february 2009 at 05:37 amfff">.
you may also try to overload regenabort in oddwfview - it seems to be called more often.
vladimir