> >4) I can't "clone" a button...
>
> I'm not sure we would add such a routine, if instead we had ways to get or
> set each of the supported attributes individually. I presume that a
cloning
> routine wouldn't be necessary in that scenario?
>
Yes. Access to the attributes would give me what I need. I would create a
"template" button, then add others using the "base" values from that one.
I'd have to rewrite my existing tight routine, but at least it would work
and be portable across releases!
> >Additional request: I'd also like to have a way to recover a Ptr by
passing
> >a function the address within a chunk.
>
> I'm not sure about this one; it would require walking the heap(s) and
would
> be less likely to be appropriate or applicable in the future. Perhaps
> since it was you who created the tSTL, you could guarantee to yourself
that
> there wasn't a prefix string...? Or depending on how many of these you
> have, it'd be easy for you to have a small table to correlate the first
> string's pointer to the handle, or even store a start pointer and a
> blocklength, just like an OS heap walking routine would do.
The problem with "guarantee to yourself that there wasn't a prefix string"
is that I won't always be in control of the creation of those tSTL's. This
is a generic "form creation" routine that has to work under all kinds of
weird conditions, and has to access resources from various providers.
Not sure why the "GimmePtrFromAddress" routine wouldn't be appropriate in
the future. Unless something MAJOR changes, we'll always refer to data
through "chunk ptrs". By having the way to recover a ptr from an address
"somewhere within" that chunk, it would save all of us developers the effort
of keeping track of those ptrs ourselves. I *hate* globals if I can avoid
them.
Thanks for your help,
Terry
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
