Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!apple!voder!pyramid!leadsv!laic!nova!darin
From: darin@nova.laic.uucp (Darin Johnson)
Newsgroups: comp.sys.amiga
Subject: Re: Workbench 1.4 suggestion
Message-ID: <491@laic.UUCP>
Date: 27 Mar 89 21:00:09 GMT
References: <5442@abo.fi> <413@antares.UUCP> <5899@abo.fi> <2064@cps3xx.UUCP> <419@antares.UUCP> <110@ssibbs.UUCP> <663@ivucsb.UUCP> <4Y=Fz7y00UkaMLBMV1@andrew.cmu.edu>
Sender: news@laic.UUCP
Reply-To: darin@nova.UUCP (Darin Johnson)
Organization: Lockheed AI Center, Menlo Park
Lines: 26

In article <4Y=Fz7y00UkaMLBMV1@andrew.cmu.edu> bader+@andrew.cmu.edu (Miles Bader) writes:
>dan@ivucsb.UUCP (Dan Howell) writes:
>> On Xerox workstations, the function of a middle button is emulated on a two
>> button mouse by pressing both buttons simultaneously.  This is called
>> "chording" the mouse.  Perhaps Intution could support this.
>
>Definitely.  [It may sound inconvenient, but in practice, it's just fine]

This may break some things.  I know of at least two programs that use
a sequence like "hold left mouse button, then click right mouse
button".  Also, holding the right mouse button and then clicking the
left means extended menu selection from Intuition.  Perhaps if
Intuition could do this if (and only if) you didn't ask about mouse
down messages.  As always, this behavior should only occur when the
program explicitly asks for it, otherwise it can break stuff.

Perhaps a simple way of doing this, without adding stuff to intuition
or breaking programs, would be to have a simple low level input
handler which returns a middle-mouse (up and down) when this happens.
This way, if anything breaks, only the user who started the input
handler is to blame.  (should be relatively simple to write using
dmouse as an example program.  The priority of the handler should be
carefully though out though.)

Darin Johnson (leadsv!laic!darin@pyramid.pyramid.com)
	Can you "Spot the Looney"?