From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Réf. : Re: [9fans] Re: moving things in a window
Date: Fri, 29 Sep 2000 10:55:18 -0400 [thread overview]
Message-ID: <20000929145519.BF8D9199E8@mail> (raw)
guess you can go a ways with xor :)
I think xor had little to do with it. You could
do it with the current draw about as easily.
It seems to have come out of the trick of looking at
the color of the pixels in your way to see if
you are going to hit anything, rather than
keeping higher-level objects.
See http://research.microsoft.com/Users/luca/Papers/Crabs/Crabs.ps
next reply other threads:[~2000-09-29 14:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-29 14:55 Russ Cox [this message]
2000-09-29 19:06 ` Theo Honohan
-- strict thread matches above, loose matches on Subject: below --
2000-09-29 13:23 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=20000929145519.BF8D9199E8@mail \
--to=rsc@plan9.bell-labs.com \
--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).