Adding the following to .Xdefaults let you use a wheel mouse without
having to run imwheel. May be it could be added in cooker?
!## NETSCAPE
Netscape*drawingArea.translations: #replace \
<Btn1Down>: ArmLink() \n\
<Btn2Down>: ArmLink() \n\
~Shift<Btn1Up>: ActivateLink() \n\
~Shift<Btn2Up>: ActivateLink(new-window) \
DisarmLink() \n\
Shift<Btn1Up>: ActivateLink(save-only) \
DisarmLink() \n\
Shift<Btn2Up>: ActivateLink(save-only) \
DisarmLink() \n\
<Btn1Motion>: DisarmLinkIfMoved() \n\
<Btn2Motion>: DisarmLinkIfMoved() \n\
<Btn3Motion>: DisarmLinkIfMoved() \n\
<Motion>: DescribeLink() \n\
<Btn3Down>: xfeDoPopup() \n\
<Btn3Up>: ActivatePopup() \n\
Ctrl<Btn4Down>: PageUp()\n\
Ctrl<Btn5Down>: PageDown()\n\
Shift<Btn4Down>: LineUp()\n\
Shift<Btn5Down>: LineDown()\n\
<Btn4Down>: LineUp()LineUp()LineUp()LineUp()LineUp()LineUp()\n\
<Btn5Down>:
LineDown()LineDown()LineDown()LineDown()LineDown()LineDown(
Alt<Btn4Down>: xfeDoCommand(forward)\n\
Alt<Btn5Down>: xfeDoCommand(back)\n
Netscape*globalNonTextTranslations: #override\n\
Shift<Btn4Down>: LineUp()\n\
Shift<Btn5Down>: LineDown()\n\
<Btn4Down>:LineUp()LineUp()LineUp()LineUp()LineUp()LineUp()\n\
<Btn5Down>:LineDown()LineDown()LineDown()LineDown()LineDown()LineDown()\n\
Alt<Btn4Down>: xfeDoCommand(forward)\n\
Alt<Btn5Down>: xfeDoCommand(back)\n
On Wed, 13 Oct 1999, Francis GALIEGUE wrote:
> Olivier Poulet wrote:
> >
> > Alessandro Sangiuliano writes:
> > > I never able to use imwheel, expecially with Netscape.
> > > Ok with GTK apps but not for the rest including KDE
> > > Starting with cooker I have discovered that running imwheel once X server is
> > > started seems to be OK.
> > > Working also with Netscape!
> >
> > Weird. I've added imwheel -k & to Xclients just before running
> > gnome-session and it works fine. Prior to that, it appeared that I had
> > the wrong mouse protocol in XF86Config. Maybe something in there ?
> >
>
> The wheel mouse is supported by X if you specify the good protocol and
> have this in your Pointer section:
>
> ZAxisMapping 4 5
