Bob, i don't understand how frmUpdateEvent impacts this.
i've implemented my frmOpenEvent handler so that it draws by basically
calling the frmUpdateEvent handler. if i remember right, this is how ToDo
does it as well.
am i missing something?
-----Original Message-----
From: Bob Ebert <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Thursday, April 01, 1999 6:55 PM
Subject: Re: FrmDrawForm changed in 3.2?
>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.
