bug#950: marked as done (CVS Emacs on Windows XP fails to draw contents of new frame)

[Emacs bug Tracking System]

Your message dated Sun, 15 Mar 2009 22:51:54 +0800
with message-id <49BD160A.6080106@gnu.org>
and subject line Re: bug#950: CVS Emacs on Windows XP fails to draw contents of 
new frame
has caused the Emacs bug report #950,
regarding CVS Emacs on Windows XP fails to draw contents of new frame
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@emacsbugs.donarmstrong.com
immediately.)


-- 
950: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=950
Emacs Bug Tracking System
Contact owner@emacsbugs.donarmstrong.com with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> CVS Emacs on Windows XP fails to draw contents of new frame
>
>
>
>
> Date: 
>
> Tue, 09 Sep 2008 12:51:22 -0400
>
>
>
>
> CVS Emacs on Windows XP sometimes fails to draw the contents of a new
> frame.  To reproduce, run "emacs -q", and evaluate this form:
>
>     (let ((frame (make-frame)))
>       (make-frame-invisible frame)
>       (make-frame-visible frame))
>
> The new frame's contents will not be drawn.  Typing "C-l" in the new
> frame does not cause its contents to be drawn.  You have to switch focus
> to another window and back again before the frame's contents are drawn.
> --
> Fran
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#950: CVS Emacs on Windows XP fails to draw contents of new frame
>
>
>
>
> Date: 
>
> Sun, 15 Mar 2009 22:51:54 +0800
>
>
>
>
> User-agent: 
>
> Thunderbird 2.0.0.19 (Windows/20081209)
>
>
>
>
> > CVS Emacs on Windows XP sometimes fails to draw the contents of a new
> > frame.
>
> This bug (also reported as bug#1748 and bug#2524) should be fixed now. 
> It was due to a poorly implemented redraw optimization within Windows, 
> which I have worked around by using a non-standard paint message 
> internally in Emacs.
>
>
>
>
> --- End Message ---