yang686526

part to pdf api
when i save as a pdf using api for part only files everything works great. now i would like it to create a 3d pdf. i know in the options under saveas when you select pdf you can check a box to save as 3d pdf. can this be done through api?
sw2007 sp5
i assume you are using c#
sldworks swapp;
swapp.opendoc6(sourcepath, (int)nativetype,
(int)swopendocoptions_e.swopendocoptions_loadmodel,
"", ref lerrors, ref lwarnings);
(swapp.activedoc)).saveas2(targetpath, 0, true, false);
you need to use the modeldoc2.extension.saveas function with exportdata. take a look at exportpdfdata::exportas3d, it is simple enough to do
why? i don't see any difference.
if you record the macro, you will see that activedoc.saveas also works.
i'd love to see you save a pdf as 3d with modeldoc2::saveas, especially considering it is 4 years out of date and if sw implemented the ability to create 3d pdfs with a function 3 years before adobe even created one i will be seriously impressed.
you said it. if 3d pdf is needed, luke is right. thanks.
i found a work around instead of the 3d pdf option. i am creating a eprt file opening it with edrawings in the backround and exporting it as a htm page to a intranet web portal.
this meets the same requirement of my engineering dept of being able to have a 3d view of a part for non pdm users.
i do notice that the eprt files are smaller 90% of the time then just a normal pdf of the same part. wonder what the 3d pdf would have ended up being in size.
luke
i think i miss read your post.
i read your second post first. you are saying it can be done correct.
"
you need to use the modeldoc2.extension.saveas function with exportdata. take a look at exportpdfdata::exportas3d, it is simple enough to do
"
i looked at all the functions and must have missed that one.
thanks
btw still using vb6.
starting the conversion to .net as soon as we finish phase one of implementation.
eric,
i also notice the sizes of edrawing files. at first i was sure they are simply a sort of link file that reads the data from the solidworks source file, but i could never seem to find or break this link to prove it, and never got around to attempting to open an edrawings file of say a complete assembly on another system detatched from the network to see if that is the case
originally posted by: luke malpass
i also notice the sizes of edrawing files. at first i was sure they are simply a sort of link file that reads the data from the solidworks source file, but i could never seem to find or break this link to prove it, and never got around to attempting to open an edrawings file of say a complete assembly on another system detatched from the network to see if that is the case
luke,
edrawings are completely stand alone files. there are no links of any kind to the sw source file.
jorn bjarning
cswp
cad & plm consultant
sw2008 sp5 / sw2009 sp2
very impressive filesize then! full 2000 part trialer assembly half a meg!