Thanks for the tip. What I just noticed is that this is only happening when
using the debug ROMs. I guess the 3.5 debug ROMs always assume the "worst
case" and actually do NOT save the screen behind the popup. The misbehavior
in my app has probably always been there, but it has never actually been
seen since a low-memory condition is usually very rare.
Doug Gordon
-----Original Message-----
From: Jean Ostrem [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 07, 2000 3:16 PM
To: [EMAIL PROTECTED]
Subject: Fwd: frmUpdateEvent and OS 3.5
>I have a form where, in addition to standard controls, I draw a couple of
>lines when the form is initialized. This worked OK up to 3.3. On 3.5 I
>notice that whenever a dialog pops up over my form (even system-controlled
>alerts, etc.), when the dialog is removed my form is restored except for
the
>drawn lines. I checked, and in the event handler for frmUpdateEvent I do
>call my function that draws the lines.
>
>Putting in a breakpoint while using POSE, I find that when I get the
>frmUpdateEvent, the entire Palm screen is blank (even the part not
>previously covered by the dialog). My line-drawing routine is then called
>and the lines are drawn on the screen. However, when I continue and return
>from the event handler, my previous screen contents now appear, but minus
>the lines that I just drew.
>
>Anyone have any idea what is going on here, and how I can get it to work
>correctly?
If you don't set handled to true for frmUpdateForm, the default form
handler handles the event by calling FrmDrawForm, which erases what
you've just drawn. You need to call FrmDrawForm, then draw your
lines, then set handled to true.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
