[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Mouse wheel
Re: Mouse wheel
Wed, 04 Jun 2003 17:04:33 -0400
> > We can then remove the (mouse-wheel-mode 1) call in w32-win.el and
> > in x-win.el we need to add:
> > (define-key function-key-map [mouse-4] [wheel-up])
> > (define-key function-key-map [mouse-5] [wheel-down])
> > (define-key function-key-map [C-mouse-4] [C-wheel-up])
> > (define-key function-key-map [C-mouse-5] [C-wheel-down])
> > ...
> > and related friends (ideally we should be able to do this mapping
> > automatically by querying the X server, but it seems difficult/impossible,
> > so for now we'll just use function-key-map). Of course, a bit more work
> > than the above is needed, but I'm just trying to see if we all agree
> > this is the way to go.
> Probably. I'm not sure what X users with >3 button mice + wheel do
> with their ZAxisMapping. There are probably enough apps that are
> hardwired to use mouse-4 and mouse-5 as the wheel, to force such users
> to go to the trouble of mapping buttons 4 and 5 to 6 and 7 so they can
> leave 4 and 5 free for the wheel.
That's already the case right now anyway. They can play around with
Emacs bindings if they prefer: the above define-key statements
shouldn't get in their way as far as I can tell.
> I thought there was a way of handling z-axis events in X directly
> without the mapping, but after searching now I think I might have
> been misled by GDK or vi documentation (both of which basically do the
> above function-key-mapping).
Indeed, it seems pretty difficult to robustly get the Z-axis events.