Yes, I'm using OS 3.3 and I believe you're right. It makes no sense to me
why it fixed it. I'll run it through the debugger a few more times to see
exactly what is going on.
Thanks,
--
Tim Astle
David Fedor <[EMAIL PROTECTED]> wrote in message news:11895@palm-dev-forum...
>
> Tim -
>
> You were seeing this in Palm OS 3.3, I presume, since that's the only os
> version where the error check is on line 1885. That error statement is in
> the TblGetItemBounds routine. The error message will be shown if the
> provided row number (that is, the parameter passed to the routine) is
> greater than the table's number of rows, or if the given column is greater
> than the table's number of columns.
>
> Having TblUnhighlightSelection fix things seems very odd - the first thing
> it does is call TblGetItemBounds itself, if the table has a selected item
> and the table is visible. So I'd guess that you might have an
> uninitialized variable or something, and this routine might be happening
to
> change something such that you get lucky.
>
> I'd encourage you to use the debugger to find out who's calling this
> routine, and why the row or column parameters are bad (or why the table
> pointer is bad!)
>
> Memory corruption and uninitialized variables are the hardest things to
> track down in C, and to me it smells like one of those situations.
>
> -David Fedor
> Palm Developer Support
>
>
>
>
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/