Re: fighting over the scroller
On Thu, 22 Sep 2011 13:41:37 -0400, "John B. Matthews"
<nospam@nospam.invalid> wrote, quoted or indirectly quoted someone who
said :
One convenient approach is to condition the property in an
AdjustmentListener:
public void adjustmentValueChanged(AdjustmentEvent e) {
isAutoScroll = !e.getValueIsAdjusting();
}
Thanks. I added that at the application level and it worked fine,
even without timers. As soon as I let go of the scroller it takes off
running automatically again.
scroller.getVerticalScrollBar().addAdjustmentListener( new
AdjustmentListener()
{
/**
* detect user fiddling with the scroller
*/
public void adjustmentValueChanged( AdjustmentEvent e )
{
userBusyScrolling = e.getValueIsAdjusting();
}
} );
The only mildly tricky part was trying to find out where I could do an
addAdjustmentListener.
--
Roedy Green Canadian Mind Products
http://mindprod.com
It should not be considered an error when the user starts something
already started or stops something already stopped. This applies
to browsers, services, editors... It is inexcusable to
punish the user by requiring some elaborate sequence to atone,
e.g. open the task editor, find and kill some processes.