My vote would be for a shared library, especially if it were possible for
the library to actuall patch the traps so that it would not be necessary to
change every call. I originally found this bug on a FrmAlert with multiple
buttons (button returning incorrect ID) so this would be an important one to
catch
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of David
Fedor
Sent: Tuesday, August 08, 2000 17:21
To: Palm Developer Forum
Subject: RE: Palm OS 3.5: FldNewField changes text on button
I've been trying to make progress on this issue. We've fixed the routines
in the OS for the next major OS release (of which we have no announcements
yet) but that wouldn't address the fact that this has existed ever since
3.0. It hardly ever was an issue until the dynamic heap started getting
large, and forms started to often need to move when adding items to the
form object.
I'm investigating the possibility of having either a static library for
developers to link into their applications, or just providing the fixed
source to compile into your applications, or something like that. Thoughts
and preferences?
Suggesting that we do a system update for every device running 3.0 to 3.5
would make some fine folks in our QA department a little annoyed at me :-(
And relatively few applications use these functions, so it might well make
sense to have this built into applications who care.
-David Fedor
Palm Developer Support
--
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/
