>>>>
CWR6, POSE 3.0.3 with the Dr4 OS3.5 debug ROMs.<<<<
I'm debugging an application that calls a form to the screen when a menu choice is made using FrmGotoForm().
During a Gremlins run, while that form was on the screen, an alarm set by the program went off and called an alert to the screen. POSE threw the following error:
Gremlin #42@908644 "Form.c, Line 801, windows cannot be under forms because they can't be redrawn."
on this line of code:
wLocalButton = FrmAlert( AlarmAlert );
I've re-read the messages on windowing as it relates to forms. I'm guessing that the problem relates to the current window and what's being drawn and where. I keep reading that I shouldn't assume that *my* form is the current form, which in this case is quite possible since this is part of an alarm routine that could be called over the top of a form in any application.
Is there something I should be doing before calling this alert?
Sorry to followup my own post, but I've narrowed the problem.
Here's how I duplicate it:
1) Set an alarm (for, say, 10 seconds from now).
2) Tap on a poptrigger so that its list is open on the screen.
3) Wait.
4) When the alarm expires and calls FrmAlert() to the screen, I tap the "OK" button to clear the alert and POSE throws the error message.
I get this message anytime I call FrmAlert() when there is a list open. I assume that it's because the open list becomes the current window and FrmAlert opens a new form on top of the window.
I can duplicate this in the OS3.5 Datebook. This leads me to believe that this is either a bug in the OS, or a bug in POSE, or that Datebook and my application share some common bug. I might add that I'm using the SDK update from the 19th.
Can anyone from Palm point me in the right direction here? I'll post this to the POSE list for Keith Rollin to look at.
Cheers,
--
Andrew Ball
[EMAIL PROTECTED]
