After I was able to get the behavior to be almost right (using lines as the
unit) by re-approximating "max value" at the moment "cur value" became equal
to "max value", I switched to chars as the unit, and it smoothed things out
to my satisfaction. I guess the approximation is better using smaller
units, and so the difference between reality and the scrollbar state is
smaller.
Thanks,
Mark Peters
in article 52016@palm-dev-forum, Steve Mann at [EMAIL PROTECTED] wrote on
6/6/01 5:13 PM:
>
>> The problem is that "the proper values" for the scrollbar's "max value" and
>> "page size" variables are always approximate. I don't know in advance of
>> rendering the entire page how many lines there are in it. Due to the
>> effects of word-wrapping (and soon font and style changes), the number of
>> characters on each line is variable.
>
> How about using the # of chars instead of the # of lines? Is that
> feasible? You can get the max # from the size of the record. All you
> need is a way to track your current char position (at least I _think_
> it should be that easy).
>
> Regards,
> Steve Mann
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/