Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!julius.cs.uiuc.edu!apple!olivea!oliveb!amiga!boing!dale
From: dale@boing.UUCP (Dale Luck)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Mouse Buttons
Message-ID: <921@boing.UUCP>
Date: 9 Dec 90 23:46:55 GMT
References: <1990Dec7.041658.14294@techbook.com> <faheyr.660601986@silver> <1990Dec7.223736.15332@engin.umich.edu> <16383@cbmvax.commodore.com>
Reply-To: dale@boing.UUCP (Dale Luck)
Organization: Boing, Milpitas, Ca.
Lines: 21

In article <16383@cbmvax.commodore.com> bj@cbmvax.commodore.com (Brian Jackson) writes:
>6.15332@engin.umich.edu> milamber@caen.engin.umich.edu (Daryl Scott Cantrell) writes:
>>86@silver> faheyr@silver.ucs.indiana.edu (Bob Fahey <NECR0SIS>) writes:
>>  To the query about 3rd mouse button (sorry, zapped it..):
>>  Hmm, the only real way to do it is by looking at hardware registers.
>
>Actually, the middle mouse button is readable under DOS 1.3. The
>message is properly sent from the input device but Intuition screens
>it out before it gets to the user. A properly written input handler
>can get at it.

Even easier is the hack I use for X. I check the qualifier bits in the
intuition message. There are three there for the state of the mouse
buttons. Although under 1.3 I can't detect a middle button event without
the mouse moving or some other intuition event, it does not seem to
be that much of a problem. It sure beat writing a input handler and a
pass around thing. Then again 2.0 or the a2024 junpstart disk, the
problem was fixed.
-- 
Dale Luck     GfxBase/Boing, Inc.
{uunet!cbmvax|pyramid}!amiga!boing!dale