BeginPaint not called on WM_PAINT

[James Hawkins]

I'm trying to get a program running called BZEdit.  Under the latest
cvs, the program shows a scrambled mess over the whole screen (I think
that is a result of this patch
http://cvs.winehq.org/patch.py?id=14725), but when I went back in time
to 2004-10-12, the only part of the screen I cant see is the part of
the screen where the map you're editing is shown.  See

http://www.artemisgames.com/BZEdit/

for screenshots.  This is the error output I'm getting.

err:msg:DispatchMessageA BeginPaint not called on WM_PAINT for hwnd 0x1002a!

This message happens every time the editor needs a repaint like when
it gets covered by another window.  Any ideas about what's going on
here?

[Robert Shearman]

James Hawkins wrote:
> I'm trying to get a program running called BZEdit.  Under the latest
> cvs, the program shows a scrambled mess over the whole screen (I think
> that is a result of this patch
> http://cvs.winehq.org/patch.py?id=14725), but when I went back in time
> to 2004-10-12, the only part of the screen I cant see is the part of
> the screen where the map you're editing is shown.

Is it possible that it is broken by this patch instead, 
http://cvs.winehq.org/patch.py?id=14371, that Paul van Schayck reported 
broke Foobar2000?
> See
>
> http://www.artemisgames.com/BZEdit/
>
> for screenshots.  This is the error output I'm getting.
>
> err:msg:DispatchMessageA BeginPaint not called on WM_PAINT for hwnd 0x1002a!
>
> This message happens every time the editor needs a repaint like when
> it gets covered by another window.  Any ideas about what's going on
> here?

Are these messages output in the 2004-10-12 version of Wine, where it 
mostly displayed properly?

Rob

[James Hawkins]

> Is it possible that it is broken by this patch instead,
> http://cvs.winehq.org/patch.py?id=14371, that Paul van Schayck reported
> broke Foobar2000?

I'll do a more regression testing to see which patch exactly broke it
completely.
> Are these messages output in the 2004-10-12 version of Wine, where it
> mostly displayed properly?

Yea these are from 2004-10-12.

[Robert Shearman]

James Hawkins wrote:
> > Are these messages output in the 2004-10-12 version of Wine, where it
> > mostly displayed properly?
>
> Yea these are from 2004-10-12.

Then that means there was already some problem with the app that has now 
been exposed. We should find out why the app isn't calling BeginPaint 
like it should.

Rob

[Mike Hearn]

On Sat, 11 Dec 2004 11:28:21 -0600, Robert Shearman wrote:
> Then that means there was already some problem with the app that has now 
> been exposed. We should find out why the app isn't calling BeginPaint 
> like it should.

Actually the code that printed that warning was removed in a recent patch.

[James Hawkins]

> Is it possible that it is broken by this patch instead,
> http://cvs.winehq.org/patch.py?id=14371, that Paul van Schayck reported
> broke Foobar2000?

The bug I was getting where the whole window is garbage is not caused
by this patch, but the error message I was getting:

err:msg:DispatchMessageA BeginPaint not called on WM_PAINT for hwnd 0x1002a!

does not show up anymore.  However, the map viewer still does not show
up as it should, and it sounds like this is that GL problem Lionel
talked about.

--
James Hawkins

[Lionel Ulmer]

> This message happens every time the editor needs a repaint like when
> it gets covered by another window.  Any ideas about what's going on
> here?

Is it using OpenGL do display the map ? If yes, it may be yet again the
known incompatibility between GL and Wine regarding multi-windowed
applications (which requires some 'hacks' in the code which may get broken
on code refactoring).

Lionel

[James Hawkins]

On Sat, 11 Dec 2004 17:51:58 +0100, Lionel Ulmer  wrote:
> > This message happens every time the editor needs a repaint like when
> > it gets covered by another window.  Any ideas about what's going on
> > here?
>
> Is it using OpenGL do display the map ? If yes, it may be yet again the
> known incompatibility between GL and Wine regarding multi-windowed
> applications (which requires some 'hacks' in the code which may get broken
> on code refactoring).
>    Lionel
>
> --
>                  Lionel Ulmer - http://www.bbrox.org/

Yes it's using OpenGL.  Can you catch me up to speed on this problem? 
btw the source is available on sourceforge.