Hi Scott,
The scrollbar arrows at the ends of the arrows are using the usual Palm
scrollbar behaviour (short 1 line code) of moving up or down a single
standard unit of scrolling, which in this case unfortunately is pixels. In
memopad, it scrolls a line since the units there are lines.
If you want to look into adding an interface for being able to set the
scroll arrows, by all means. It is probably best to make it selectable if
you do, so people can set it according to their wishes.
In the auto_scroll branch of the Plucker CVS, there is a form ready to add a
gateway to this (form is called autoscroll & scroll options--it currently
just has the autoscroll, setting the scrollbar arrows wasn't put in yet).
The form was formatted to allow extra room for controls to set the
scrollbars. Can just make that form taller, then use the same type of line
as
"Autoscroll Jump:" [selection box] \/Pixes/Pages
for a
"ScrollArrow Jump:" [section box] \/Pixels/Pages
The code for handling the spinners and popup boxes (which need a little
touching-up to be more readable and extensible) can then just be reused. New
preferences (scrollarrow jump and scrollarrowpixel/page) have to be added to
the end of the list of preferences, to handle upgrades from older Plucker
versions.
There will likely be a Handera version at some point, so have to be able to
deal with different screen resolutions. Handling a PenDown in the area of
the scrollarrow (which I didn't feel like doing) was the only initial way I
could think of doing it, but I didn't look into it any farther. Accessing
and or/modifying attributes of the scrollbar directly are also not a good
option since those would break in Palm OS 5.0 when it comes out.
Best wishes,
Robert
> I'm new to plucker. In general it's pretty quick but
> the one problem that stands out for me is that scrolling
> using the tappable arrows at either end of the scrollbar
> is very very slow. As a palm developer I'd be more than
> happy to look into that, but I don't want to collide with
> any other ongoing development/modification efforts.
>
> Is this problem currently on someone's turf? Is it up for
> grabs? How do I go about co-development with this stuff?
>
>
> Scott Herman
> Yale New Haven Hospital
> Department of Lab Medicine
> 20 York Street
> New Haven, Ct. 06504
> (203) 688-2449
> [EMAIL PROTECTED]
>
