Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!cs.utexas.edu!asuvax!ncar!gatech!prism!dali.cc.gatech.edu!iansmith
From: iansmith@dali.cc.gatech.edu (Ian Smith)
Newsgroups: comp.sys.next
Subject: Re: X11
Keywords: X11 buttons
Message-ID: <1991May31.090550@dali.cc.gatech.edu>
Date: 31 May 91 13:05:50 GMT
References: <1991May29.151312.15680@serval.net.wsu.edu>
Sender: news@prism.gatech.EDU
Reply-To: iansmith@warhol.gatech.edu
Organization: Software Engineering Research Center's Multimedia Lab
Lines: 36

In article <1991May29.151312.15680@serval.net.wsu.edu>,
hakimian@tek4.eecs.wsu.edu (Karl Hakimian - staff) writes:
|> I have mouseX running on a NeXT cube. Everything seems find except I
can't
|> figure out how to get the NeXT mouse to act like a three button mouse
instead
|> of a two button mouse. Does anyone have any idea?
|> 
|> -- 
|> Karl Hakimian
|> hakimian@yoda.eecs.wsu.edu
You can't (with the current implementation). A process is snarfing
the NeXTStep events off the window server, shoving them down a pipe to
the the X server then dispatching them to X clients.  Until NeXTStep
supports generating a button three mouse event,you are pretty much
hosed... however...

An adventurous soul might be able to hack the server source to do 
something like what the old HP's used to do, ie. hitting both buttons
together gives button 3.  I really don't like this solution much, but
it would work.  You could look in the dispatching code (look for a
giant switch statement somewhere in $(TOPDIR)/src/mit/server/ddx/next,
I can remeber the exact file).  I would prefer hacking the keycode
table
to lose a keycode and using that as a mouse button. 

If I get a few free minutes, I post the diffs.
ian

--
"Daddy what's regret?"
"Well son, all I can say is its always better to regret something you
have
done, than to regret something you haven't done. And, if you see you
mother
this afternoon..."  --Gibby