I actually took some time out of my day (that I probably shouldn't have) to track down the issue and submitted a patch (<a href="http://www.winehq.org/pipermail/wine-cvs/2009-January/052045.html">http://www.winehq.org/pipermail/wine-cvs/2009-January/052045.html</a>). Not everything in the WMF files renders properly but at least Wine doesn't crash horribly, for now I've just pre-rendered the WMF files (we're distributing computers to students with this software, so we want things to look right). Also, there is a 15 day trial of the software :)<br>
<br>Erich Hoover<br><a href="mailto:ehoover@mines.edu">ehoover@mines.edu</a><br><br><div class="gmail_quote">On Wed, Jan 21, 2009 at 11:03 PM, Rolf Kalbermatter <span dir="ltr"><<a href="mailto:r.kalbermatter@hccnet.nl">r.kalbermatter@hccnet.nl</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">Erich Hoover wrote:<br>
<br>
>I ran into an issue with WMF files in helping someone get an application to<br>
>work (Athena Visual Studio) and I worked around it by pre-rendering the<br>
>application's vector WMF files. I don't currently have the time to resolve<br>
>the issue, but for when I do I'm curious whether there is a reason that<br>
>OleLoadPicture* has been implemented manually. It seems that the LGPL<br>
>"libwmf" has excellent support for both bitmap and vector WMF files (it at<br>
>least worked for converting the files I had trouble with!), so it seems to<br>
>me like it would make sense to use this library rather than spinning a<br>
>separate implementation. Any comments are appreciated.<br>
<br>
</div>Do you have somewhere the specific WMF file in question? The license is a<br>
"bit" to expensive to buy it just to test this ;-)<br>
<font color="#888888"><br>
Rolf Kalbermatter<br>
<br>
</font></blockquote></div><br>