Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-22 Thread John Ehresman
Tor Lillqvist wrote: Owen Taylor writes: > There is a third possible issue - if you are moving another window over > a window, does windows send: > > ERASEBKGND > ERASEBKGND > ERASEBKGND > PAINT > > Or is ERASEBKGN only sent immediately before PAINT? If I understand correctly, WM_E

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Tor Lillqvist
Owen Taylor writes: > There is a third possible issue - if you are moving another window over > a window, does windows send: > > ERASEBKGND > ERASEBKGND > ERASEBKGND > PAINT > > Or is ERASEBKGN only sent immediately before PAINT? If I understand correctly, WM_ERASEBKGND is sent whe

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Tor Lillqvist
John Ehresman writes: > There's a patch for this at > http://bugzilla.gnome.org/show_bug.cgi?id=144269 Ah yes, thanks for the pointer... I should have remembered that there already was discussion in bugzilla about WM_ERASEBKGND. --tml ___ gtk-devel

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread John Ehresman
Tor Lillqvist wrote: It was suggested to me on IRC that it is unnecessary (thanks!), and it indeed seems so. There's a patch for this at http://bugzilla.gnome.org/show_bug.cgi?id=144269 It's definitely needed to eliminate flickering when widgets are interactively resized. There were issues wit

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Ivan Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | A typical win32 double-buffering program | may do nothing with WM_ERASEBKGND but return with a non-zero. s/double-buffering program/program that uses backing store/ erase_background() is one of the source of flickering (e.g. during toplevel resize). -

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Owen Taylor
On Mon, 2005-03-21 at 07:46 -0500, Owen Taylor wrote: > On Mon, 2005-03-21 at 12:53 +0200, Tor Lillqvist wrote: > > It was suggested to me on IRC that it is unnecessary (thanks!), and it > > indeed seems so. > > > > But anyway, before I zap it, a request to fellow gtk/win32 hackers: > > Please ver

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Tor Lillqvist
Owen Taylor writes: > You certainly can't do that on windows that don't have have expose > events in their event mask, since they'll never get repainted. Note the suggestion isn't doing anything to the WM_PAINT handling. Can you think of some test corner cases in gtk-demo, testgtk or elsewhere?

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Owen Taylor
On Mon, 2005-03-21 at 12:53 +0200, Tor Lillqvist wrote: > It was suggested to me on IRC that it is unnecessary (thanks!), and it > indeed seems so. > > But anyway, before I zap it, a request to fellow gtk/win32 hackers: > Please verify. Comment out the WM_ERASEBKGND case in gdkevents-win32.c: > gd

Re: Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Ivan Wong
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 | But anyway, before I zap it, a request to fellow gtk/win32 hackers: | Please verify. Comment out the WM_ERASEBKGND case in gdkevents-win32.c: | gdk_event_translate(). My local copy of the gtk+ binary which is used to debug Gnumeric/Win32 has erase_bac

Drop WM_ERASEBKGND handling in gdkevents-win32.c?

2005-03-21 Thread Tor Lillqvist
It was suggested to me on IRC that it is unnecessary (thanks!), and it indeed seems so. But anyway, before I zap it, a request to fellow gtk/win32 hackers: Please verify. Comment out the WM_ERASEBKGND case in gdkevents-win32.c: gdk_event_translate(). (Please test in the gtk-2-6 branch, as the HEA