Date: Thu, 27 Jun 1996 08:24:15 +0200 (MET DST) From: sos@FreeBSD.ORG To: dawes@rf900.physics.usyd.edu.au (David Dawes) Cc: sos@FreeBSD.ORG, joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Subject: Re: moused conflicts with X11 Message-ID: <199606270624.IAA04754@ra.dkuug.dk> In-Reply-To: <199606270119.LAA09419@rf900.physics.usyd.edu.au> from "David Dawes" at Jun 27, 96 11:19:12 am
next in thread | previous in thread | raw e-mail | index | archive | help
In reply to David Dawes who wrote:
>
> >However I dont see that the Xserver should be changed, as they will
> >see /dev/mouse as a say mousesystems mouse, no matter what mouse
> >actually is on the system. That would also ease the X installation
>
> If it is done this way, how do you plan to deal with 2-button mice?
> Would 3-button emulation be included as an option, or would the X server
> still do that? How would the 2 buttons be mapped? What about a mouse
> that has more than three buttons (I don't know if the mousesytems protocol
> supports more than three or not).
Erhm, the mousesystems protocol was just an example, if another std. one
seems more suited, we'll take that one. As for 2 button mice, yes
moused supports 3-button emulation.
> >for J. Randomuser. And besides I dont see the need for Yet Another
> >Mouse Interface (YAMI), when we can just use one of the de facto
> >standards. We also would have a BIG problem with commercial progs
> >that way, so lets not get that insane...
>
> I agree with this.
That makes two....
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Soren Schmidt (sos@FreeBSD.org) FreeBSD Core Team
So much code to hack -- so little time.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199606270624.IAA04754>