Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!execu!sequoia!texbell!bellcore!aardvark!john
From: john@aardvark.ctt.bellcore.com (John Letourneau)
Newsgroups: comp.windows.news
Subject: Re: Help with double-click recognition.
Message-ID: <18034@bellcore.bellcore.com>
Date: 24 Oct 89 13:40:39 GMT
References: <603@granite.dec.com> <1922@bacchus.dec.com> <1490@esquire.UUCP> <6564@ficc.uu.net> <17943@bellcore.bellcore.com> <6594@ficc.uu.net> <18015@bellcore.bellcore.com> <6650@ficc.uu.net>
Sender: news@bellcore.bellcore.com
Reply-To: john@aardvark.UUCP (John Letourneau)
Organization: Bell Communications Research, Piscataway, NJ
Lines: 19

In article <6650@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>(Personally, I think click-hold is the *only* way to drag... this click
> here with this button move click there with that button stuff is strictly
> for the birds. Down with control-alt-meta-cokebottle-hold-your-face-right
> sequences).
	AH!!! We agree! In fact this is part of my "anti-menu" feelings when
	it comes to "common" window activity. I know, what's common for you
	may not be for be for me (iff 8^)). Even though calling up a menu and
	doing a selection is just a matter of clicking (single and/or multi)
	there is still an element of mouse movement. MY feelings are that this
	counts as a "key-stroke". Your "choose these windows" now "do this"
	paradigm is OK...actually something I may concider for some applications
	I've been concidering. Well, I'm tired of talking about this for today.
	Later.........

-_ .- _ *  - ~ _______   "I feel the need...       | John P. Letourneau
 . * = _ .~ _ / 9000  \___  the need for speed!!"  | john@ctt.bellcore.com
~_ .~_ .  =  /    Turbo   \                        | Bellcore
~. - _ = * - \-O------O----|                       | Piscataway, NJ.