🚀 go-pugleaf

Hi Ed,
Thanks alot for your reply. I hope you're doing right.

Well, you said that the outline was part of the non-client area. You're
right, it's precisely the reason why I wondered why the outline wasn't
drawn when I handled WM_PAINT (thru calls to BeginPaint/EndPaint). I do
not handle the WM_NCPAINT message. Ok, I will ask the question differently.
What is the difference between BeginPaint/EndPaint and GetDC/ReleaseDC
in a WM_PAINT message handler ?

In order to repaint the window, I've called InvalidateRect with the 3rd
parameter set to TRUE, meaning I want to erase the background. Everything
is erased except the static controls' captions, this means that when I
change the captions with SetWindowText, the old caption is still behind
the new one.

I've processed the WM_ERASEBKGND message by returning a non-zero value
without success. Anyway, I repeat that static controls are the -only-
components that pose a problem. All other components of the group box
(lines and rectangles) are erased fine before they are drawn again.

Once again, you're right, when you call SetWindowText, Windows should
clear the background by itself before showing the new text. But in my
application, Windows clearly doesn't ! I have to iconize the window,
then open it up again in order to see the labels displayed right.
Though, my program doesn't specifically handle this situation, the
WM_PAINT is just sent once again to my application. I think it must
be due to a bug of Windows.

Don't worry, Ed, I'm not a newbie, I always keep win32.hlp at hand. ;-)

Have a nice day,
Mark