AFAIK, FM15 is not "aware" of the type of the graphic object that sits inside an anchored frame. Embedded graphics appears as OLE2. Is there a way to programmatically extract embedded Visio graphics from Framemaker files and leave all other types of graphics in place?
Thank you for your responses in advance!
Hi Roman, What do you mean by extracting the embedded graphics? Thanks. -Rick
Thank you for your response!
"Embedded" means not linked/imported by reference - just sitting locally in a FM file.
There is no path data stored for embedded graphics that can be retrieved programmatically. So there is no way to convert them to referenced graphics.
Thanks for your prompt response, Rick!
I remember seeing a post regarding a framescript created by GolehTek that was supposed to extract graphics from an FM file. I've never seen the script itself and this company no longer exists. Did you have a chance to test this script?
An embedded Visio object can be opened from Framemaker or edited withing Framemaker by using the corresponding context menus. So why can't this action be mimicked with a script? Going back to my original question, can ES identify the type of graphics put within an anchored frame (i.e., whether it's a jpeg or vsd)?
Thanks for your response!
I did test this script in FM10 and it worked partially (didn't support Visio graphics). In FM15, it does not work at all. I guess it's because of the DLL file called by the script.
No direct experience, but some suggestions:
Thank you for looking into this issue. Are the embedded figures treated as insets by FrameMaker?
I'll try to play around with these APIs.
The above is extrapolated from the C API, with which I am more familiar. But I've not used insets very much, so I'd trust the manuals over anything I say.