Sorry I don't have the original report, it was submitted on the web site.
The problem is in the routine
PrvFixupPointers
This routine runs through the form looking at 32 bit quantities to see if
they are pointers that need fixups because some of the
Form data was moved to make room for the new object. Unfortunately it does
not know anything about the structure of the data, it just does a range
check assuming that it is a pointer. I found it because I happened to have a
controlID which was being changed because
The 32 bit quantity picked up just happened to fall into the range it was
checking.
-----Original Message-----
From: David Fedor [mailto:[EMAIL PROTECTED]]
Sent: Monday, June 28, 1999 18:40
To: [EMAIL PROTECTED]
Subject: RE: Need location of Desrossiers' DynamicUI article
>It may also be tempting to create forms dynamically by using the 'New'
>functions in OS 3.0 (FrmNewForm, CtlNewControl, etc.) but be warned that
>there is a bug int the OS rom code for creating new objects (yes it has
been
>reported) which makes these routines verry error prone.
Perhaps you could expand on the description of the problem you saw - these
routines do work extremely well in many cases, and are used extensively in
the Palm VII for example. I'm not sure what bug you are referring to, or
if you're more talking about an app design issue.
Besides, if there was a serious bug like you're implying, I would have
thought it would have been fixed in 3.1 or 3.2 or 3.3... if it was reported
it to ears willing and able to do something about it. Like mine, for
instance, or many other folks on this list. So please explain...
Thanks
-David Fedor
Palm Developer Support
