Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!rutgers!sri-spam!ames!ucbcad!ucbvax!ZERMATT.LCS.MIT.EDU!RWS
From: RWS@ZERMATT.LCS.MIT.EDU (Robert Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Proposed Protocol Change to WarpPointer
Message-ID: <870801105100.4.RWS@KILLINGTON.LCS.MIT.EDU>
Date: Sat, 1-Aug-87 10:51:00 EDT
Article-I.D.: KILLINGT.870801105100.4.RWS
Posted: Sat Aug  1 10:51:00 1987
Date-Received: Sun, 2-Aug-87 09:47:54 EDT
References: <8708010352.AA00968@puppy.io.uucp>
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 21


    Date: Fri, 31 Jul 87 23:52:51 EDT
    From: Kimbo Peebles-Mundy <io!puppy!kimbo%ileaf.uucp%umb.umb.edu@RELAY.CS.NET>

    The Interleaf system frequently makes use of relative displacements of
    the mouse.  This is done in our popup code when traversing levels in the
    menu tree, and in diagramming, when creating objects.

These still seem like cases where, before you issue the warp, you know
where the pointer was, so you know absolutely where it should go to, and
if it has since been moved far from that position you probably don't
want to move it at all.

							   If that weren't
    enough, we also use small deltas to greatly improve the "feel" of the
    system; for example, within a level of the popup tree, if the motion is
    mostly vertical, then the horizontal component is canceled out.  This
    make tall menus much easier to navagate.  I can't see any way this kind
    of correction could be done with an absolute warp.

Ah, now this sounds like a reasonable example.