[GRASS-dev] Re: your change broke the scroll bars another way

[Maris Nartiss]

Hello Michael,
on my Linux box Your change made mouse scrollbar useless - it was just
stopping at two positions - top and bottom. To get to middle of
scrollable view I had to use those clickable areas (dunno their name).
Previous version, that I restored, was working just fine - now again I
can scroll with mouse wheel or clickable area. Seems like keyboard
arrows are not working :(
I reverted my local copy - keyboard arrows still doesn't work and
scrolling is only useable with clicking or dragging scrollbar. Mouse
roller is not useable, as it works like Home/End keys in other apps.
Hm. Home/End/PageUp/Down keys also doesn't work.
I would assume there's some problem with Tcl/Tk version You use on
Mac, as there was some reason why such code was working for years in
Linux version. I'm running 32bit Gentoo with tcl-8.4.19
As current Tcl/Tk GUI development is almost frozen and if problems
arise from newer tcl/tk versions (>8.4), I would propose to freeze
GRASS tcl/tk requirements to 8.4.

Summary:
Scrolling with keyboard doesn't work (#435)
Old scrolling code doesn't work for some reason on Macs

Other developers, please, make some tests and report results:
cd grass64_release/lib/gtcltk
svn up -r 35413
make
gis.m
add a raster layer and try to scroll lower pane (Display raster layer)
and raster map selection window (Select Item - Raster Map). Does
scrolling is smooth or jumpy?
close gis.m
svn up -r 35412
make
gis.m
repeat tests. Has scrolling changed? Better or worse?
Report results to -dev list or to me directly. Don't forget to write
Your OS and Tcl/Tk version.
Thank You!

Markus - this issue needs to be solved before 6.4.0 goes final. Minor
but really annoying issue.

Maris.

2009/1/16, Michael Barton <michael.barton at asu.edu>:
> Maris,
>
> Your reversion of my change in select.tcl broke the scroll bars for
> activation by the mouse scroll wheel. Now the scroll wheel will make
> the thumb go up but not down. What problem does your change fix? If we
> need to find a different solution that solves both problems, that's
> fine. But please don't assume that my change was for no reason at all.
>
> Michael
>
>