Return to BSD News archive
Xref: sserve comp.windows.x.i386unix:16955 comp.unix.bsd.freebsd.misc:2817
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!daffy!uwvax!uwm.edu!psuvax1!news.ecn.bgu.edu!vixen.cso.uiuc.edu!howland.reston.ans.net!xlink.net!rz.uni-karlsruhe.de!news.uni-ulm.de!news.belwue.de!fu-berlin.de!cs.tu-berlin.de!fauern!news.tu-chemnitz.de!irz401!uriah.heep!bonnie.heep!not-for-mail
From: j@bonnie.heep.sax.de (J Wunsch)
Newsgroups: comp.windows.x.i386unix,comp.unix.bsd.freebsd.misc
Subject: Re: Serial Mice and Xfree
Date: 3 Jul 1995 09:57:25 +0200
Organization: Private U**x site, Dresden.
Lines: 34
Message-ID: <3t87t5$2uk@bonnie.tcd-dresden.de>
References: <3sumb0$sbd@CUBoulder.Colorado.EDU> <3t0lpr$lgn@bell.maths.tcd.ie>
Reply-To: joerg_wunsch@uriah.heep.sax.de
NNTP-Posting-Host: 192.109.108.139
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Robert Walsh <rjwalsh@maths.tcd.ie> wrote:
>I'm having the same problem under FreeBSD 2.0.5-RELEASE and the version
>of XFree86 that came with it (is this version 3.1.1?). I've tried it
>both with a Microsoft serial mouse and a Microsoft PS/2-style mouse.
>Both gave the same problem: I have to move the mouse to make it
>recognise that I've just clicked a button. So I did some experimenting
>and noticed the following:
You should get a real mouse with 5 buttons instead. :-) (The X
protocol defines up to 5 buttons.)
As you've noticed, this is a problem with the 3-button emulation.
After you've pressed the first button, the emulator is not yet able to
decide if it will become an event to emulate the third button, or it
will remain an event for this button.
> + When I run some programs, such as Xman and Tk programs,
> certain strange things start to happen.
This is the FAQ of the month now. Turn off NumLock, and/or fix the
broken translation tables in the offending clients to properly ignore
the <NumLock> modifier where they ought to be. (Btw., this is also
apparent e.g. on SGI Irix. So if you've fixed them, be sure to file
the diff back to the XConsortium.)
As a temporary hack-around, you can enable the ``ServerNumLock''
kludge in your XF86Config file. This makes the NumLock key no more
a modifier key.
--
cheers, J"org private: joerg_wunsch@uriah.heep.sax.de
http://www.sax.de/~joerg/
Never trust an operating system you don't have sources for. ;-)