At 4:48 PM -0800 4/1/99, Scott Johnson wrote:
>I guess "similar" here means "just like this example but with the draw
>calls reversed", eh? :-) :-)
Hmmm. This could be a problem...
In the frmUpdateEvent case, you don't necessarily have to worry about the
bitmap under problem because the form has already been opened and is
visible on screen, so presumably you're drawing over the already drawn form.
*some* piece of code has to erase the form's boundary area before the form
is drawn, at least once. So you'll want to be careful to make sure that
your drawing happens after the erasure, but before the form is drawn.
I think some of us here would really like it if FrmDrawForm could be the
thing that erases the form bounds. ...that simplifies a lot of code. But
if that's true, then anything drawn before FrmDrawForm will be overwritten.
--Bob
