From: Adrian Tritschler <Adrian.Tritschler@its.monash.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Mouse cursor is too large.
Date: Thu, 3 Oct 2002 08:46:47 +0000 [thread overview]
Message-ID: <ang7h0$lb7$1@towncrier.cc.monash.edu.au> (raw)
In-Reply-To: <45e22e468ef7fee73c6fdab5bf945f7e@plan9.bell-labs.com>
Russ Cox wrote:
> You're right -- there's only one switch in s3load.
> There used to be identical redundant ones. I forgot
> that the second got replaced by the dolock variable.
Phew, I'm not going crazy. 8904 seems to be the ID for the S3 83C366, but
adding it to vgas3.c doesn't make any difference.
> When you move the mouse over a window border,
> does the cursor change at all? (On a system with a
> working cursor, the cursor changes to indicate that
> you can drag the window border to resize the window.)
Yep, I always get the correct cursor, it changes when it should, its just that
it is the top-left 16x16 pixels in the 64x64 block of noise. The remaining
block never changes. I'm guesing that somewhere there is a registry setting
for a 64x64 hardware cursor, and it was never initialised to all be transparent.
Um, as asci-fied below. + is the cursor, the spaces are transparent, X is the
black and white noise.
+X X
X X
Adrian
---------------------------------------------------------------
Adrian Tritschler mailto:Adrian.Tritschler@its.monash.edu.au
---------------------------------------------------------------
next prev parent reply other threads:[~2002-10-03 8:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-02 16:26 Russ Cox
2002-10-03 8:46 ` Adrian Tritschler [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-03 14:25 Vester Thacker
2002-10-02 16:09 Russ Cox
2002-10-01 23:16 Russ Cox
2002-10-02 16:17 ` Vester Thacker
2002-10-01 15:22 Russ Cox
2002-10-01 23:04 ` Vester Thacker
2002-10-02 9:01 ` Adrian Tritschler
2002-10-01 13:11 Vester Thacker
2002-10-01 14:51 ` Philippe Anel
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='ang7h0$lb7$1@towncrier.cc.monash.edu.au' \
--to=adrian.tritschler@its.monash.edu \
--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).