At 16:16 2001/03/22 -0800, you wrote:
>Ok, it seems clear, then, that the problem must have to do with your
>HoleViewLoadDataFunc function, which gets called by the system when the user
>selects a table cell. A quick look at the documentation for the
>TableLoadDataFuncType reveals that the dataH parameter must be an "Unlocked
>handle of a block containing a null-terminated text string." You state that
>your gLabels, which is what you assign to the dataH, contains "20-odd bytes
>of storage".
>
>So perhaps your problem is that those 20-odd bytes are not a null-terminated
>string?
Thanks, Jim,
I'm presuming that the StrCopy/StrPrintF functions that are used in the
load callback null-terminate their output. The string display properly
on-screen. The globally-declared handles are unlocked, although I seem to
recall that locking them when they were allocated (and before they were
used to build the table) made no difference.
I've tried to delve into the ToDo code to see if I'm doing the same things,
but has been mentioned before on this list, it is meaty code - difficult to
extract the bare-bones call sequences to get something to work. Does anyone
know of any tutorial code on tables (i.e., nix scrolling, on/off columns,
etc.)?
Cheers, Erik
-------------------------------------------------------------------
Icefield Tools Corporation tel: (867) 633-4264
3C Glacier Road fax: (867) 633-4217
Whitehorse, Yukon CANADA e-mail: [EMAIL PROTECTED]
Y1A 5S7 internet: http://www.icefieldtools.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
