I discovered the nifty little system function known as MemSetDebugMode
today. I've been having fun with that.
Interestingly, if I set the debug mode with the following bits:
memDebugModeCheckOnChange
memDebugModeScrambleOnChange
memDebugModeAllHeaps
...guess which system function I run into trouble with?
FrmRemoveObject. It gives me the following error in POSE:
Chess Client (1.1.d.18) called SysFatalAlert with the
message: "Form.c, Line:6135, Form shouldn't move".
Is this as unexpected as I think it is? I thought the whole point of
calling FrmRemoveObject with a pointer-to-a-pointer was that the form
*could* move?
Okay, maybe I am just an easily-frustrated newbie, but doggone it, this
thing just doesn't make sense sometimes. :-)
--Larry
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
- FrmRemoveObject Nicolas Raitman
- Re: FrmRemoveObject Arvind
- RE: FrmRemoveObject Richard Burmeister
- RE: FrmRemoveObject Manikumar Kandhasamy
- Re: FrmRemoveObject Nicol�s Zeitlin
- RE: FrmRemoveObject Nicolas Raitman
- FrmRemoveObject Larry Gilbert
- Re: FrmRemoveObject Matt Graham
- Re: FrmRemoveObject Larry Gilbert
- Re: FrmRemoveObject Matt Graham
- Larry Gilbert
