From owner-freebsd-current Tue Jun 25 01:36:58 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id BAA02234 for current-outgoing; Tue, 25 Jun 1996 01:36:58 -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 BAA02203; Tue, 25 Jun 1996 01:36:46 -0700 (PDT) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.6.11/8.6.9) id SAA03634; Tue, 25 Jun 1996 18:36:41 +1000 From: David Dawes Message-Id: <199606250836.SAA03634@rf900.physics.usyd.edu.au> Subject: Re: moused conflicts with X11 To: sos@FreeBSD.org Date: Tue, 25 Jun 1996 18:36:41 +1000 (EST) Cc: current@FreeBSD.org In-Reply-To: <199606250658.IAA15097@ra.dkuug.dk> from "sos@FreeBSD.org" at Jun 25, 96 08:58:42 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-current@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >In reply to David Dawes who wrote: >> >> >Because the way I understand it, its because BOTH mosed & X has the >> >mousedevice open at the same time, this is only fixable by having >> >one of then close it. BUT the X server NEVER closes it during its >> >life time :( >> >> That isn't true for the XFree86 servers. They close the mouse device >> when switching away from the X server. They do this so that other things >> can use the mouse (eg, an X server running on another vty). > >Great !, thanks for the enlightment, it has to be my old'ish Xaccel >server that does wierd things. Now that I have your attention, how >would you guys prefer to talk to the mouse ?? It would be nice if there was an option to have the OS do the protocol translation, and provide a device from which the translated mouse events can be read. SVR4, SCO and Mach (and OS/2, I think) do this sort of thing. gpm on Linux provides a device (probably a pipe, I don't know the details), which gives output translated to MouseSystems format regardless of the native mouse type. David