Thanks for the replies. It reassures me that I'm not going crazy.
Have any of you tried your code (dynamic creation and removal of form
objects) on the 3.5 debug color ROM? On this ROM, I get "has just read
from an unallocated chunk of memory." when adding a control. I think it is
probably because this ROM is configured to test low memory conditions and
the bug is causing some other problems but what can we do about it?
It looks like I may have to try other alternatives as this method does not
seem too stable.
Thanks,
-Ken
> ----------
> From: Keith Wolcott[SMTP:[EMAIL PROTECTED]]
> Reply To: Palm Developer Forum
> Sent: Monday, September 11, 2000 9:42 PM
> To: Palm Developer Forum
> Subject: Re: FrmRemoveObject() quirk
>
> Yes, it is the PrvFixupPointers bug (search the archives for more
> information). Another way around the problem is to use
> FrmHideObject and FrmShowObject.
>
> Keith Wolcott
>
> Sally Anne Palmer wrote:
>
> > 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.
>
>
> --
> 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/
