I actually took some time out of my day (that I probably shouldn't have) to
track down the issue and submitted a patch (
http://www.winehq.org/pipermail/wine-cvs/2009-January/052045.html). Not
everything in the WMF files renders properly but at least Wine doesn't crash
horribly, for now I've just
Erich Hoover wrote:
>I ran into an issue with WMF files in helping someone get an application to
>work (Athena Visual Studio) and I worked around it by pre-rendering the
>application's vector WMF files. I don't currently have the time to resolve
>the issue, but for when I do I'm curious whether t
On Thu, Jan 15, 2009 at 8:38 PM, Erich Hoover wrote:
> I ran into an issue with WMF files in helping someone get an application to
> work (Athena Visual Studio) and I worked around it by pre-rendering the
> application's vector WMF files. I don't currently have the time to resolve
> the issue, bu
detail is, itself, different between 9x and
NT). For compatibility, Wine needs detailed control over its WMF
reading and rendering, and it needs to expose this to apps that will
misuse it in strange ways.
OleLoadPicture* does not need such things. If oleaut32 were the only
place where Wine needed WMF
> It seems that the LGPL "libwmf" has excellent support for both bitmap
> and vector WMF files (it at least worked for converting the files I had
> trouble with!), so it seems to me like it would make sense to use this
> library rather than spinning a separate implementation. Any
> comments are ap
I ran into an issue with WMF files in helping someone get an application to
work (Athena Visual Studio) and I worked around it by pre-rendering the
application's vector WMF files. I don't currently have the time to resolve
the issue, but for when I do I'm curious whether there is a reason that
Ole
