Roger Chaplin,
First, thanks for your suggestion, it is a good temporary solution!
but.....
On Sat, 22 Apr 2000 11:01:40 -0400, you said:
> You need to call FrmDrawForm before you can call WinEraseLine (or any
> other OS routine that changes the visible content of the form).
Okay that is a good system for both OS's (though not _required_ in 3.3)
So now we have.....
FrmInitForm
FrmSetactiveForm // alows you to draw in OS3.3
FrmDrawForm // to alow me to draw in OS3.5
for (j = 0;j<160;j++)WinEraseLine(0,j,159,j);
// this line is required to erase the previous
// form which is not erased with FrmDrawForm
// in OS3.3. the Form is just drawn over the top of
// the previous form. This line gives you a clean slate.
// possibly FrmEraseForm would be better
FrmDrawFrom. // to get the form elements back on there
<other windows drawing code if needed>
--------
My question is, is it really necessary to cal DrawFormTwice? my form is
complicated and it takes a second or so to draw. Having to wait for it
to draw and then erase and then draw again causes a noticeable delay and
messes up that "seemless" integration look so often referred to in thhe
programning manuals.
derik
email: [EMAIL PROTECTED]
WWW: http://www.pobox.com/~derik
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
