On Tue, Feb 26, 2002 at 10:17:55AM -0700, Dave Brown wrote:
> I'm trying to use FrmNewBitmap to dynamically display a bitmap on a form.
> The bitmap displays fine but my lists become corrupted. If I take the
> FrmNewBitmap call out the lists are fine so I know it's the cause.
And later:
> It actually doesn't work with the 4.0 ROM either. Adding them dynamically
> does it though.
This bug is what the 4.1 overview of fixes [1] is talking about when it
says (modulo corrections)
Using the dynamic UI creation routines did [not] work properly
when there was a list on the form with static entries created in
Constructor [or another resource compiler].
Fixed in 4.1. There was a palm-dev-forum thread about this about a year
ago (when some developer found the bug), but the archives are at the
other end of my cellphone at the moment, so I can't find it just now :-).
IIRC Palm noted at the time that the workaround was to do your lists
dynamically too if you were going to use dynamic UI on a form with
lists. Alas.
And Terry Dennis replied:
> Interesting. I'm not sure which release fixed that PrvFixUpPtrs glitch.
If you grep the MacsBug strings in the ROMs, you'll see that
PrvFixupPointers() exists in all the 3.x ROMs, but was replaced by
PrvRewireForm() in 4.0. You might infer that PrvRewireForm was a
complete rewrite of the earlier function, with its own (different, and
smaller) set of bugs. (Can someone tell us what's in the 3.5.2 patch?
I'm not especially familiar with it.)
ISTR that this particular bug was not in the PrvFixupPointers()
implementation, and was new to 4.0.
John
[1] http://palmos.com/dev/support/docs/palmos40/os41overview.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
