Maybe some of you can learn from my mistake. Usually we want the OS to
handle an event after we have processed it; however, sometimes we don't! The
only case that I have worked with before now has been to tell the OS not to
handle lists for which I have created a callback draw function. I have found
an additional exception in the context of a modal form handler. To dismiss
the modal form and return to the main form, I called FrmReturnToForm when
the user taps a button. Then FrmValidatePtr would tell me that my form
pointer was null. At first, I thought it referred to my main form, but then
it dawned on me that the OS was trying to handle the button after the modal
form was deleted from memory. The problem disappeared, along with the modal
form, when I set handled = true. So there you have it.
Oh, the humbling road to enlightenment...
--
Gary R. Miller, Jr.
i.Consultant
Wireless Practice
CIBER, Inc.
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
