"Chris DiPierro" <[EMAIL PROTECTED]> wrote in message
news:36414@palm-dev-forum...
>
> Yea it is. I appreciate it.
>
> Ok, here's a question then.
>
> After many Gremlins I see a lot of chunks that are unlocked (#0), owned by
> my app (#2) and have 'fM' set on them, each of which is '0x64 requested
> bytes' and actually '0x6c alloced bytes"
>
> If I dump the memory they contain, it looks like menu items from various
> menus in my application. Unfortunately, this list just keeps growing and
> growing. This seems odd because although I do have a bunch of forms and
> menus, the navigation between them is purely through FrmGotoForm and
> FrmPopupForm coupled with FrmReturnToForm ... according to the docs, both
of
> these should handle the destruction of menus associated with each form.
Yet,
> it doesn't seem to be the case because I can see menu items leftover from
> old forms when the app's on a completely different form...
You do know that FrmReturnToForm doesn't send a frmClose event to your form,
so any cleanup you would normally do there should be done before the call to
FrmReturnToForm. The only difference between FrmPopUpForm and FrmGotoForm
is that FrmGotoForm posts the frmCloseEvent to the current form before
posting the frmLoad and frmOpen events to the new form. FrmReturnToForm
kills the active form using FrmEraseForm and FrmDeleteForm, then activates
the topmost form left on the screen.
--
Ben Combee
Veriprise Wireless <http://www.veriprise.com>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
