-
Bug
-
Resolution: Won't Fix
-
P4
-
None
-
1.1.6
-
x86
-
windows_nt
Name: chT40241 Date: 06/17/98
ScrollbarPeer should surface setVisibleAmount (and setValue, setMinimum, and setMaximum rather than just setValues (value, visibleAmount, min, max)).
In some views, the visibleAmount can change during the scroll. For example, in a table view with non-uniformly sized columns or rows. Without the ability to independently set the visibleAmount, the view is forced to specify a value. Well in the case of a scroll thumb drag where the view is receiving a succession of AdjustmentEvents of type TRACK, this passed value may inadvertently reset the thumb position as the scrollbar is already ahead of the view (e.g. generated a second AdjustmentEvent while the view is still processing the first). This causes the scroll thumb to not move smoothly on a drag, but to jump back-and-forth.
======================================================================