yang686526

dwfimport
dwfimport
hello support,
i'm using dwgdirect1.13 library of purpose import attched dwf document. could you please take look at the attachment? i'm worry about performance of dwfimport method execution, it takes about 1.5~2 min with odamfc application. could you please let me know if there any optimizations steps on the client and library side possible? actually, native viewers take no more than 5~10 seconds to parse attached file.
reading forum information i've found that next 1.14 build of dwgdirect library, especially dwfimport() will be based on dwftoolkit7.0. my question if it will improve performance of dwfimport functionality and what else benefits we may expect?
thank you in advance!
vasyl.
attached files
in general cad objects created during conversion dwf to dwg are much more "heavier" than display primitives which are processed by dwf viewers.
and number of duplicated url increases from entity to entity.
dwf toolkit 7 is still in beta. for now we can't say which dwf toolkit version will be used in dd 1.14.
most likely dd 1.14 will have dwf import/export based on dwf tookit 6 and windows beta using dwf toolkit 7.
i don't think that moving to v7 will significantly increase performance. the main benefit would be support for 3d dwf.
sergey slezkin
hello sergey,
thank you very much for this information! could you please let me know how will be perfomance increased without duplicate url's? just on your mind please.
could you please let me know if any of more od products support direct dwf rasterization?
best regards,
vasyl.
quote:
originally posted by sergey slezkin
in general cad objects created during conversion dwf to dwg are much more "heavier" than display primitives which are processed by dwf viewers.
and number of duplicated url increases from entity to entity.
dwf toolkit 7 is still in beta. for now we can't say which dwf toolkit version will be used in dd 1.14.
most likely dd 1.14 will have dwf import/export based on dwf tookit 6 and windows beta using dwf toolkit 7.
i don't think that moving to v7 will significantly increase performance. the main benefit would be support for 3d dwf.
entity urls are stored as array of strings. as array grows while appending entries one by one memory is reallocated multiple times. surely several hundreds of urls attached to the same entity is not a usual situation.
currently oda has no direct dwf rasterization.
sergey slezkin