- From: Irene Vatton <irene.vatton@inrialpes.fr>
- Date: Thu, 14 Nov 2002 09:46:39 +0100
- To: vanandel@ucar.edu
- Cc: vanandel@atd.ucar.edu, www-amaya-dev@w3.org
On Tue, 12 Nov 2002 17:13:54 -0500 (EST) Joe Van Andel <vanandel@atd.ucar.edu> wrote: > > I built Amaya on RH 7.3, with the options > ..../configure --prefix=/usr --with-gtk --with-dav > > (gtk-config --version shows 1.2.10) > > As I scroll a document, the size of the scrollbar oscillates, and my > position in the document jumps. Amaya doesn't build the whole document image but only the part which is displayed. When you scroll, Amaya removes the undisplayed part of the document image and regenerates the new necessary part. The scroll slider represents the displayed part in the whole document file (not the whole document image because for large documents the whole document image doesn't exist). That explains why the slider size changes when you scroll the document. This method works in general but not always. Sometimes we have a problem with scroll events. When the user moves the slider, Amaya updates the document image and generates a new slider position and slider size. Sometimes after the update the slider is no longer at the current mouse position and the scroll widget, even if it knows that the slider was modified by the application, continues to generate events which add extra scrolls up and scrolls down. Probably the solution is to change the mouse position when the slider is updated, but that's not easy to do. > I also built amaya 6.4 without specifying the --with-gtk option, and the > scrollbar acts the same way. > > > -- > Joe VanAndel > National Center for Atmospheric Research > http://www.atd.ucar.edu/~vanandel/ > Internet: vanandel at ucar dot edu > > "There are only 10 kinds of people in the world -- > Those who understand binary, and those who don't." > > -- Irene.
Received on Thursday, 14 November 2002 03:46:47 UTC