Steve, Of course it doesn't serve a purpose it is a simple case of something you would need to do. IE Allocate memory when creating dynamic UI elements. "The whole thing falls apart..." means it doesn't work. In this overly simple case you can run the app once then the second time the Palm resets. I would say that means the "whole thing falls apart"...
I would appreciate it if others would try this simple example and tell me if they can recreate the problem, Scott said he tried it using GCC and it worked fine. I have found that the bug depends on the positioning of the memory allocations. You can allocate then deallocate memory before you create and destroy and Dynamic UI element, as well as allocate and deallocate memory after you create and before you destroy the Dynamic UI element. The problem only seems to occur if you allocate memory then create a dynamic UI element, then try to deallocate the memory. NOTE: no errors occur during the first execution only on the second (or third if you use a C base instead of a C++ base). Richard ----- Original Message ----- From: "Steve Mann" <[EMAIL PROTECTED]> To: "Palm Developer Forum" <[EMAIL PROTECTED]> Sent: Monday, November 19, 2001 3:40 PM Subject: Re: Bug? With creating Dynamic UI Controls > >The whole thing falls apart with > >successfully creating and destroying the controls when I allocate other > >memory structures. > > What falls apart? How do you know? What does that mean? Specifics please. > > >TestHandle = MemHandleNew(10); > . > . > . > >MemHandleFree(TestHandle); > > Why do you do this? As far as I can tell, it serves no apparent purpose. > > Regards, > Steve Mann > > -- > 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/
