From owner-freebsd-current Wed Jun 26 18:19:35 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA10308 for current-outgoing; Wed, 26 Jun 1996 18:19:35 -0700 (PDT) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id SAA10299; Wed, 26 Jun 1996 18:19:22 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id LAA09419; Thu, 27 Jun 1996 11:19:12 +1000 From: David Dawes Message-Id: <199606270119.LAA09419@rf900.physics.usyd.edu.au> Subject: Re: moused conflicts with X11 To: sos@FreeBSD.ORG Date: Thu, 27 Jun 1996 11:19:12 +1000 (EST) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG In-Reply-To: <199606260659.IAA26099@ra.dkuug.dk> from "sos@FreeBSD.ORG" at Jun 26, 96 08:59:12 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >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). >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. David