Xref: utzoo comp.windows.x:14544 comp.windows.news:1597
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!cs.utexas.edu!execu!sequoia!texbell!bellcore!aardvark!john
From: john@aardvark.ctt.bellcore.com (John Letourneau)
Newsgroups: comp.windows.x,comp.windows.news
Subject: Re: Help with double-click recognition.
Message-ID: <18033@bellcore.bellcore.com>
Date: 24 Oct 89 13:32:51 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> <18005@bellcore.bellcore.com> <6648@ficc.uu.net>
Sender: news@bellcore.bellcore.com
Reply-To: john@aardvark.UUCP (John Letourneau)
Organization: Bell Communications Research, Piscataway, NJ
Lines: 49

In article <6648@ficc.uu.net> peter@ficc.uu.net (Peter da Silva) writes:
>In article <18005@bellcore.bellcore.com> john@aardvark.UUCP (John Letourneau) writes:
>>   OK, OK, Sorry, Sorry...position should be DRAG! sheesh
>
>OK, I understand now. You have select/drag/menu. I don't know... I don't
>move windows around that much, so I can't see giving a mouse button up for
>that action. I'd rather use a poke point.
	Weeeell we've got 100+ host on our network; Sun 3's, 4's, sparcstations,
    Pyramids, uVaxes, 3B2s, and on, and on. I typically have over 5 windows
    up at least, doing different things. FOR ME, moving windows or selecting
    them to be unobscured is how I choose to work as oppose to icons opening
    and closing. Besides I haven't had the time to hack up a "something has
    happened in the window represented by this icon" code...ie. missing some
    host event when the icon is up.
>
>hit PERFORM. On the Mac, SELECT is a mouse click and PERFORM is a double
>click. I'd rather make PERFORM a seperate button.
    Well, YOU prefer the Mac look. Aren't user programmable interfaces neat?!
>
>Implementation detail. I didn't say "top", I said "obscured". You can tell if
>a window is obscured either by looking at the clipping list for that window,
    Hmmmmmm
>
>Not really. If you *think* of the action as being in the time domain, it
>can be annoying to people whose perception of the time domain is different
>from yours. If everything depends only on a sequence of actions, instead
>of worrying about just when the actions occurred, it's a lot easier on the
>programmer and the user.
    Ah, I doubt if we'll agree completely (at all?) on some of these points.
    Maybe not even on the magnitude of their importance. End Of Comment (EOC)
>
>>   PS. The click and move can get trickey if framebuffer interrest are
>>     used for things...trust me on this I tried it.
>
>Now it's my turn... what does this refer to?
    I was afraid you'd ask this...let's see...Ah, I have it set up so that
    a select click on the framebuffer will open another window on my Sun.
    When things are slow for whatever reason, I'll click on an existing
    window frame to unobscure it..I then move the mouse (just slightly) so
    that it is on the framebuffer..I get a new window instead. This is what
    I've observed, it doesn't make complete sense to me, I haven't had time
    to dig into it. It might vary well be a figment of my imagination, or
    a subtle difference between what event is actually used->down or up
    transition. Sorry I can't be any more specific than this.

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