This is mostly informational, as I can avoid the problem:
When I have a button that switches forms (say formA to formB), and formA
event handler returns a 0 (event not handled to allow button to highlight
and unhighlight) I get an error (presumably becuase by the time the event is
passed to the system the button no longer exists). So, on these types of
buttons one must return true from the form event handler? This seems just a
bit hostile on the PalmOS side, as the error message resulting does not give
many clues as to why it is happening.
example code:
<from formA event handler>
case ctlSelect:
{
cid = e->data.ctlEnter.controlID;
if(cid == SwitchFormBtn)
{
FrmGotoForm(formB);
gCurrentView = formB;
handled = 0;
}
break;
}
return handled;
Am I correct in my deduction? Did I miss something in the docs, or is this
the kind of thing that is considered too obvious for documentation?
Paul
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
