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?
--Jim Preston
"Erik Blake" <[EMAIL PROTECTED]> wrote in message
news:43199@palm-dev-forum...
>
> At 11:05 2001/03/22 -0800, you wrote:
> >Well, it's unclear exactly what you mean by "until the user
> >selects/highlights a text cell for the SECOND time". Does that mean that
if
> >the user just taps twice in succession on the same cell, you see the
error?
> >Or that the user taps on one cell, then on a different cell, then back to
> >the first cell and then you see the error?
>
> The second of the three options, if you'll pardon the pun. User selects
one
> text cell, then another, then back to the first. Then the error occurs.
>
> The error also occurs if you leave the form and reenter the form within
one
> application execution (note that the snippet I posted does not have this
> capability - it's a bare-bones program to try to isolate the problem).
> Selecting any of the text cells that were selected the first time the form
> was displayed immediately cause the error.
>
> I also notice that when emulating with a IIIc debug rom, the selected rows
> appear to have a pink background, rather than white, after they have been
> selected and then another cell is selected - i.e., the backgound is a
> different colour after the highlighting goes away. I'm not sure what this
> signifies.
>
>
> >comment out the call to FldSetSelection to see of that makes the error go
> >away.
>
> I have tried this, but it has no effect. The problem was occurring before
I
> added this line.
>
> It seems that the OS is somehow trying to modify the text contained in the
> memory allocated for the handles, but as far as I can tell, it should not.
> But even if it did, there is plenty of room allocated for the text and
> null-terminator. The handles all appear to be valid, even when the errors
> are occurring.
>
> I guess the problem is that I don't understand the error message -
"Invalid
> length" is not terribly illuminating. As I said, there should be lots of
> room in the memory chunk for the text I am placing there (and not, I
think,
> changing in any way). Yet, if I select "Continue" on the Emulator's error
> dialog, I get "Memory reallocation error". As far as I can tell, no
> reallocation is required!
>
> Any ideas? I have not reposted the code snippet.
>
> 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/
