At 2:11 AM -0800 11/19/99, Steve wrote:
>Now that you mention this, I look at code in several of my apps and
>sometimes I'm returning true after processing frmUpdateEvent and
>sometimes false. I have no idea why, and I can't say that it has
>mattered, at least so far as I've noticed. Anyone care to shed any light
>on why this might (or might not) matter?
I just ran into a problem in my app where it was returning handled=true after handling
a frmUpdateEvent. It worked fine until I tested it using the new 3.5 debug ROM. This
ROM doesn't use the saved bits (although it does allocate them), even when there's
enough memory to do so. The idea is to expose problems which would otherwise only
occur when memory is low. By returning true after updating the table, I was preventing
the OS from updating the form title, and other simple widgets. Try your apps on this
ROM and I suspect it'll display incorrectly after dialogs go away on those forms where
your frmUpdateEvent handler returns true.
-
Danny Epstein, Applied Thought Corporation
Have friends with Palm organizers? Get BeamBooks!
http://www.appliedthought.com/beambooks
