Hi Peter,
What I meant by the first statement was a nice way of saying that a Device
Context does exist in .net, and the Graphics object does encapsulate it's
functionality, that's all I meant by that scenario.
I do like your second option with WM_PAINT, though.
On MSDN documentation it says that there are 4 types of Device Contexts, 2
obvious
Display, Printer, the third being a memory DC.......
The documentation states that if you use a memory DC and have your
application write to this vs a Display DC, the output is rendered, captured
and never shows, because you by-passed the Display device. Maybe I read to
much into this, but it sounded as though there was a way to set this Device
Context so that your app renders to a device of choosing. Unfortunitley the
documentation pretty much stopped there, and not going into how to change the
default funtionality of rendering to a Display DC.
Thanks
Nick