9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] mouse vs key
Date: Mon, 21 May 2001 16:24:49 +0000	[thread overview]
Message-ID: <3B093A87.353E15C7@null.net> (raw)
In-Reply-To: <0ced01c0e131$f8853360$e8b7c6d4@SOMA>

Boyd Roberts wrote:
> i do remember thinking (when i was using the blit) that
> i wish that damn code would give me back my mouse!  then
> you'd make a massive overcorrection and the mouse cursor
> would be anywhere except where you wanted it to be.

The way we implemented cursor hysteresis (using a tablet pen
rather than a mouse) in the PEAC system, for example in
locking onto menu items, was simply to track the actual
locator device coordinates all the time but "snap" the
displayed cursor location to whatever grid once we were
within lock range of a grid position (e.g. something like
1/2 of an item width for menus).  That is much better than
adjusting the locator coordinates to always match the jumped
cursor location.  Our users were very happy with the
behavior: solid visual feedback when an item became
clickable, a "dead space" around the exact grid location
within which small locator motions would not change what
was clicked on, and continuous locator mapping into the
display space so that one's motor intentions were always
consistent with observed behavior.


  reply	other threads:[~2001-05-21 16:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-20 13:18 rob pike
2001-05-20 13:37 ` Boyd Roberts
2001-05-21 16:24   ` Douglas A. Gwyn [this message]
     [not found] <rob@plan9.bell-labs.com>
2001-05-20  0:16 ` [9fans] ls -m rob pike
2001-05-20  1:38   ` [9fans] mouse vs key Scott Schwartz
2001-05-20  6:29     ` Dan Cross
2001-05-20  8:09     ` Matt H
2001-05-20 12:50       ` Boyd Roberts

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3B093A87.353E15C7@null.net \
    --to=dagwyn@null.net \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).