W3C home > Mailing lists > Public > www-amaya@w3.org > January to March 2000

Re: 2.5pre: other scrolling problems.

From: <Irene.Vatton@inrialpes.fr>
Date: Tue, 14 Mar 2000 15:14:24 +0100
Message-Id: <200003141414.PAA10493@tahiti.inrialpes.fr>
To: Eddie Maddox <eddie@mngovsci.com>
cc: Irene.Vatton@inrialpes.fr, WWW-Amaya List <www-amaya@w3.org>
In-reply-to: Your message of Mon, 13 Mar 2000 12:55:00 -0500."
             <Pine.LNX.3.96.1000313120703.26035F-100000@ns1.greenbush.com> 

> I did more testing on this and the "wild ride scrolling" and found that
> CTRL-UP and CTRL-DN scroll pretty smoothly. Nice. Perhaps the plain UP and
> DN code could learn something from CTRL-UP and CTRL-DN. 
> 
> Gary Klesczewski mentioned the trick of touching the mouse button after
> you stop scrolling to have the text cursor be positioned on screen again
> where you just scrolled to. This works very nice, too. 
> 
> Perhaps we could combine these: have the text cursor UP and DN keys
> function as CTRL-UP and CTRL-DN do until you stop scrolling. Then the text
> cursor is automatically placed on the screen somewhere. 

CTRL-UP and CTRL-DN scroll up and dowm but don't move the current selection.
UP and DN move the selection then scroll if necessary. The bug occurs in the
part of the code that checks if the scroll is necessary or not.
As Amaya works on partial formatted document, it believes that it's the end 
or the top of the document and doesn't scroll.
I know exactly where the bug occurs. I just need time to fix it.
Thanks for the bug analysis

> Selection is done with SHIFT-arrow-key, so there should be no confusion
> here for Amaya. 
> 
> ------------------
> Eddie Maddox
> eddie@mngovsci.com
> 
> 
> 
> 
> 

  Irene.
Received on Tuesday, 14 March 2000 09:15:53 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:53:21 UTC