Hi Ken,
I've been having the same problem this past week and it seems to be a bug in
the FrmRemoveObject function related to a PrvFixupPointers function which it
calls. Unfortunately there seems to be no way to get around this bug and so
you must remove the objects in reverse order. I ended up removing all the
objects from the form and then placing back on all the objects except the
one I wanted to remove, it's a bit of dodgy workaround and a lot of work to
remove just one object but it works.
BTW There was some discussion about this problem a while back so you could
search through the archives for more info.
Hope this helps,
Sally-Anne.
> -----Original Message-----
> From: Yu, Ken [IT] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, 12 September 2000 0:48
> To: Palm Developer Forum
> Subject: FrmRemoveObject() quirk
>
>
>
> I am using FrmRemoveObject() to remove dynamically created objects
> (controls, fields). It seems that I must remove them in the
> reverse order
> that they were created. If not, I get a "App has just read
> directly from
> memory manager data structures.". I see no mention of this
> behavior in the
> docs. Can anyone shed some light as to what's going on? I'm
> using with GCC,
> POSE, 3.5 color ROMS.
>
> Thanks!
>
> -Ken
>
>
> --
> For information on using the Palm Developer Forums, or to
> unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
