"Gary Gorsline" <[EMAIL PROTECTED]> wrote in message
news:61672@palm-dev-forum...
>
> Here's one I can't seem to find. This is a follow-up to the
"Philosophy of
> Forms VS Dialogs" thread. Dave Feddor indicated that for the
situation that
> a dialog would be fine.
>
> Problem. Main Form has button that starts a Dialog. Main Form and
Dialog
> have their own event handlers. Main Form does not have Save Behind
checked.
> Dialog does have Save Behind checked. The first time the dialog is
> activated from the Main Form and then released (e.g. Dialog's event
handler
> does not handle the "done" button - e.g. passes a handled as false),
the
> main form is redrawn AOK. However, on the 2nd and subsequent calls to
the
> dialog (from the button being pressed again on the Main Form),
remnants of
> the dialog screen are kept (as if it was now part of the save behind
image)
> and the main form is redrawn with these pieces of characters showing
up in
> between fields. These remnants are not from the dialog that just
completed,
> but rather the dialog call that occurred the time before this dialog
call
> (one call behind).
Are you creating the dialog, then modifying its controls, then calling
FrmDoDialog? If so, you could have display problems as indicated here.
To solve this, call FrmDrawForm on the dialog right after creating it,
then modify your controls, then call FrmDoDialog. The problem is that
some control functions draw themselves even when they aren't yet
visible. The code that does the save behind is in FrmDrawForm, so a
preemptive draw will ensure that the correct data is saved.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
