DoubleBuffering replaces old C style flipping??

[aewarnick]

Does

 

this.SetStyle(ControlStyles.DoubleBuffer, true);

this.SetStyle(ControlStyles.AllPaintingInWmPaint, true);

 

automatically draw the object to the background and then show it to the screen; therefore eliminating the need to draw a backbuffer like in C++?

[mutant]

Yeh, thats its job.

[Volte]

You need to do all your painting in the OnPaint event though for it to be effective. Just call 'this.Invalidate()' to cause OnPaint to fire.

[aewarnick]

That sure makes things aaaaaalllllot easier. Thanks.

[aewarnick]

Another good question. What is the point or advantage of setting the

AllPaintingInWmPaint flag when DoubleBuffer should be enouph. It just does not make sense to me yet.

 

And if you set AllPaintingInWmPaint you must also set UserPaint as well!

 

What is the advantage of declaring more than DoubleBuffer?

[mutant]

If you set AllPaintingInWmPaint you should set UserPaint to true too. AllPaintingInWmPaint prevents the background from being earased so it reduces flicker.

[Volte]

Just be careful about that one, though, as setting UserPaint to true on an already existing control will cause Windows to completely ignore it when it goes about painting your form; it will just be a small patch of garbled image and you'll need to do *all* of the control's painting yourself.

[aewarnick]

But I have to set UserPaint to true don't I (that is, if I set AllPaintingInWmPaint to true)?

[mutant]

You should set UserPaint to true if you use AllPaintinginWM.

[aewarnick]

I know that is what the documentation says. Thanks!