> I don't think there will ever be a problem with memory allocation and the
> handler field. The OS always has to convert between the resources and the
> internal representation, so even if gadgets didn't have a handler field in
> previous OS version, they do in 3.5.
I was wrong on this one; I did more digging and found that the FormType
image in memory is basically a copy of the resource with various internal
fields fixed up. This means that only a dynamically created gadget has
space for the handler, which would explain why they didn't made
resource-instantiated gadgets extended.
However, I've found that almost anything you can do with an extended gadget
can be done with a normal gadget and glue code, and it will work on older OS
versions as well. I'm glad Palm tried to be innovative here, but with the
limitations, I don't really see what adding the whole extended gadget
concept bought them.
--
Ben Combee
Veriprise Wireless <http://www.veriprise.com>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
