Eric House wrote:
> I'm using the 0.5 version (gcc 2.7.2.2-base) and have never used the
> PROLOGUE macro. I'm not using drawing callbacks, e.g. for lists, but
> I certainly use form handlers. And I've shipped several apps to
> thousands of users none of whom's complained about a crash.
Have you run your app on the debug ROM? I used to think I didn't need
CALLBACK_PROLOGUE on form handlers, but then I found crashes when I ran
on the debug ROM. As I understand it, in "normal" situations, after a
popup like the Find dialog is dismissed, the system repaints the
underlying form with a saved copy of the image. However, if memory is
low and the system can't save the underlying image, it insteads sends a
frmUpdateEvent to the app. For some reason I don't totally understand,
in the situation where the form's UpdateEvent handler is called, the
CALLBACK_PROLOGUE/EPILOGUE is required. The kicker is, the debug ROM
*always* uses the frmUpdateEvent mechanism rather than repainting with a
saved image, so you'll see this right away.
--Mark
