Quote Originally Posted by Senith View Post
Also if I misunderstood your post please let me know .
I think it's possible that you might have misunderstood. As requested by JohnCz, please post code. Not the actual code of your project, but simple code that demonstrates the flicker that you are encountering.

Generally speaking, with no special effort at all, a resizable dialog will not show any appreciable flicker until there are maybe 50-80 controls on it simultaneously. I don't think you have that many controls. And note that I said that "no special effort" is required for flicker-free performance. Just ensure that WS_CLIPCHILDREN is set. So the fact that you are seeing significant flicker, and the fact that WS_CLIPCHILDREN made it worse, tell me that there is something wrong with the overall architecture, fundamentally.

You state that you are using "actual" controls ("actual" meaning that the controls have their own WndProcs that are probably the default WndProcs supplied by Windows). If so, you are somehow overriding the WM_PAINT messages sent to the controls themselves, and somehow painting the controls in a doulbe-buffering mechanism in the WM_PAINT handler for the parent dialog. Please let us know (show the code) if you are using some abomination like a SendMessage of WM_PAINT to the control from within the WM_PAINT handler of the dialog, like so:
Code:
// from the WM_PAINT handler of the parent dialog
// pseudo-code

hdc = BeginPaint()
hdcMem = create memory device context

SendMessage( hwndControl_1, WM_PAINT, hdcMem, 0L );
SendMessage( hwndControl_2, WM_PAINT, hdcMem, 0L );


BitBlt( hdcMem into the hdc );

ReleaseEverything
EndPaint();
If you are doing something like this, then it's not a wonder that there is flicker.

Mike