However, FrmHideObject and FrmShowObject do not destroy the object where as I wished to actually remove the object and free memory etc that it is occupying and refering to. If you are dynamically creating and deallocating objects then you need to do this rather than just hiding the objects and freeing them all at the end. With such scarse memory resources I want to keep as much memory available during the program execution as possible, so if my object is not needed anymore then I want to get rid of it as soon as possible and make that memory available straight away.
Sally-Anne. > -----Original Message----- > From: Keith Wolcott [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 12 September 2000 11:42 > 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 ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
