>> On Mon, Nov 19, 2001 at 03:05:35PM -0600, Richard Bell wrote:
>>> I've got this down to the simplest case and hopefully someone knows
>>> something about this. What I'm doing is populating a form with controls
>>> based on settings in a database. The whole thing falls apart with
>>> successfully creating and destroying the controls when I allocate other
>>> memory structures.
Since the well-known problems [1] with dynamic UI involve memory corruption
dependent on the numerical values of pointers, it's not surprising that
your program works or not depending on what other memory you happen to
allocate when, or that other people can't reproduce your problems.
On Mon, Nov 19, 2001 at 04:25:09PM -0600, Richard Bell wrote:
> I'm using Code Warrior 7.0 and SDK 4.0 running on POSE 3.3 with an OS 4.0
> ROM. But you have made me curious as to an issue with Code Warrior instead
> of Palm OS.
However, I'm a little surprised that you're seeing these effects on 4.0,
which has a completely different (and smaller) set of dynamic UI bugs
from 3.0--3.5.2.
It would be interesting to see what results you get with 3.5.3 or 4.1.
If 4.1 is what I think it is, it has no dynamic UI bugs. (Yeah, right,
like I won't get proved wrong on that one! :-))
John
[1] Search the archives for obscure keywords like "dynamic UI" and
"FrmRemoveObject".
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
