Thanks for the tip (actually, I had just come to the same
conclusion by debugging through the OS code).
However, I'm still mystified. It's my *initial form* that's
being closed. Why the attempt to do a redraw of the nothing
that's behind it (the saveBehind attribute is not set, BTW).
In fact, if my app's very first statement is
FrmAlert(RomIncompatibleAlert);
it generates the same error message ("Form.c,
Line:649..."). Something fundamental seems broken.
At 11:20:58 -0800 on Thu, 27 Jan 2000, [EMAIL PROTECTED] wrote:
>It's because FrmHandleEvent calls FrmEraseForm in its handling
>of frmCloseEvent.
>FrmEraseForm calls the relevent redraw function (the one that
>reports the
>problem).
>
>-- Keith
>
>
>Greg Lutz <[EMAIL PROTECTED]> on 01/26/2000 09:28:40 PM
>
>Please respond to "Palm Developer Forum" <[EMAIL PROTECTED]>
>
>Sent by: Greg Lutz <[EMAIL PROTECTED]>
>
>
>To: "Palm Developer Forum" <[EMAIL PROTECTED]>
>cc: (Keith Rollin/HQ/3Com)
>Subject: Another Debug-ROM catch
>
>
>
>
>I have an application which, when run on the emulator (recent
>vintage) with an OS 3.5 debug ROM (ColorDbg.rom, for instance),
>reliably generates the following error message:
>
>Form.c, Line:649, Windows cannot be under forms because they
>can't be redrawn.
>
>I had been assuming that this was due to the debug ROM forcing
>form update events instead of simply restoring saved pieces of
>bitmap, to test applications' handling of those events. But it
>turns out that a frmCloseEvent, not a frmUpdateEvent, is being
>handled when this message pops up.
>
>Can I get some advice on debugging it?
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
