msg 14 (WM_ERASEBKGND) not supported yet

[Blake McBride]

Greetings,

I have a Win32 app I wrote in C. I compiled the source code for Wine
without a problem. The app appears to run fine but it spits out:

fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet

I checked all of my code and nowhere do I use WM_ERASEBKGND. Can someone
give me a hint on how to get rid of this annoying message?

Thank you.

Blake McBride
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-us ... chment.htm

[jeffz]

Greetings,

I have a Win32 app I wrote in C. I compiled the source code for Wine
without a problem. The app appears to run fine but it spits out:

fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet

I checked all of my code and nowhere do I use WM_ERASEBKGND. Can someone
give me a hint on how to get rid of this annoying message?

Thank you.

Blake McBride
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-us ... chment.htm

it's just an informational message, if you don't want to see it then set the environment variable WINEDEBUG to -all

WINEDEBUG=-all wine foo.exe

[Blake McBride]

Thanks for the input but I' rather not requre every user of my software to
set an environment variable. Since I have the source to my app isn't there
something I can change about my app to not do whatever is causing the
problem?

Thanks.

Blake
http://blake.mcbride.name


On Mon, Dec 1, 2008 at 6:18 PM, jeffz <[email protected]> wrote:

Blake McBride wrote:

Greetings,

I have a Win32 app I wrote in C. I compiled the source code for Wine
without a problem. The app appears to run fine but it spits out:

fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet

I checked all of my code and nowhere do I use WM_ERASEBKGND. Can someone
give me a hint on how to get rid of this annoying message?

Thank you.

Blake McBride
-------------- next part --------------
An HTML attachment was scrubbed...
URL:

http://www.winehq.org/pipermail/wine-us ... chment.htm


it's just an informational message, if you don't want to see it then set
the environment variable WINEDEBUG to -all

WINEDEBUG=-all wine foo.exe

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.winehq.org/pipermail/wine-us ... chment.htm

[vitamin]

Thanks for the input but I' rather not requre every user of my software to
set an environment variable. Since I have the source to my app isn't there
something I can change about my app to not do whatever is causing the
problem?

I doubt. You have full source of Wine as well. You can find where it's coming from and fix it. Or just tell your users to ignore those messages, since Wine can print much more meaningless messages.

[James McKenzie]

Blake McBride wrote:

Greetings,

I have a Win32 app I wrote in C. I compiled the source code for Wine
without a problem. The app appears to run fine but it spits out:

fixme:msg:pack_message msg 14 (WM_ERASEBKGND) not supported yet

Do you change the background anywhere in your program code?

You might also want to look at the code generated by any pre-processors.

James McKenzie

[DaVince]

WM_ERASEBKGND is probably something used by Wine or somewhere deeper rooted into system functions that you use. In any case, it's likely something that has to be fixed inside Wine rather than your app.