[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

lynx-dev Re: Lynx, X, and wheel mouse

From: Webmaster Jim
Subject: lynx-dev Re: Lynx, X, and wheel mouse
Date: Wed, 19 Jul 2000 17:01:14 -0400

On Wed, Jul 19, 2000 at 02:15:59PM -0500, Klaus Weide wrote:
> On Wed, 19 Jul 2000, Webmaster Jim wrote:
> > ! Lynx wheel mouse
> > lynx*vt100.translations: #override\n\
> > Shift<Btn4Down>,<Btn4Up>: string("(")\n\
> > Shift<Btn5Down>,<Btn5Up>: string(")")\n\
> These would be "trapped" in form input fields...
> > Ctrl<Btn4Down>,<Btn5Up>: string("^B")\n\
> > Ctrl<Btn5Down>,<Btn4Up>: string("^F")\n\
> And these would act differently in form input fields, too
> (but maybe that's actually desirable.)

The main use I see for the wheel is easy scrolling on long pages of
text. I wouldn't expect people to need the wheel in input fields. Of
course, if they type a lot of text they may be tempted to try to scroll
back up.

> > <Btn4Down>,<Btn4Up>: string("^P")\n\
> > <Btn5Down>,<Btn5Up>: string("^N")\n\
> > The shift and ctrl combos don't work as expected, but the simple wheel
> > motions translate to DOWN_TWO and UP_TWO properly.
> Only if you have "Emacs keys" OFF.  And again, may be different
> in form input fields.

Yes, I assume users who try to use the mouse wheel know they need to see
what key mapping within Lynx may be active.

Marvin the Paranoid Android says:
I ache therefore I am.  Or in my case, I am therefore I ache.

; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to address@hidden

reply via email to

[Prev in Thread] Current Thread [Next in Thread]