Hmmm, dunno. I don't think it is, because otherwise when I forced a refresh (by covering up and uncovering it, or switching desktops) it would render correctly. This isn't the case here - it simply does not render until something inside the plugin causes a refresh: an animation for instance, or toggling the antialiasing.
I really need a Windows painting guru to explain to me exactly what WM_ERASEBKGND does, MSDN didn't clear things up for me at all
thanks -mike
On Tue, 2002-12-03 at 16:25, Paul Millar wrote:
On 3 Dec 2002, Mike Hearn wrote:
It sends WM_PAINT, the does the NCPAINT thing which seems to be do do with window borders, and then some ERASEBKGND messages come from somewhere. I have a sneaking suspicion that the background gets erased after it's painted and not before, but that's a total shot in the dark and the absence of flicker kind of makes my theory look not so strong.
Well, speaking in ignorance (I freely admit to it ;) it *could* have something to do with problem 2 of:
http://www.winehq.com/hypermail/wine-devel/2002/11/0803.html
corruption when dialogue boxes are moved around. I tried it again today (with cvs a few days old) and the problem still exists.
Paul Millar