yang686526

dwgdirect(odt3) memory footprint
dwgdirect(odt3) memory footprint
has any one compared the file size and memory footprint between odt2 and odt3 ?. the libs in odt3 seems much bigger(odt2.x 3mb odt3 14mb). my current application is a nice 1mb and i'm wondering if this will dramatically changed. also, we run on pocketpc which only has 32mb...so far i get the impression this may not work now.
any views ?.
thanks, dawson

the dwgdirect libs are a lot bigger than 2.0 (they also do a lot more than 2.0). we haven't looked at the memory footprints yet, but we will be doing so in the near future.
pocketpc support is questionable at this point. the first hurdle that we saw with it is that dd uses stl, which is not available with microsoft's compiler.


the size of application linked with static library greatly depends on subset of functionality used. if your application was satisfied with c toolkit functionality surely not all 14m will be linked. btw, the size of odamfcapplib - sample application statically linked with dwgdirect is about 2.5m and it can load/save/recover/audit, perform conversions between r12,13,14,15 and draw a little.
sergey slezkin