From: paurea@gsyc.escet.urjc.es
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Bug report
Date: Mon, 6 May 2002 03:42:46 +0200 [thread overview]
Message-ID: <15573.57238.155353.295574@nanonic.hilbert.space> (raw)
In-Reply-To: <818a4b58332c9faa04a62c3ebaeb5250@plan9.bell-labs.com>:Russ Cox's message of 19:24:29 Sunday,5 May 2002
Russ Cox writes:
> From: "Russ Cox" <rsc@plan9.bell-labs.com>
> Subject: Re: [9fans] Bug report
> Date: Sun, 5 May 2002 19:24:29 -0400
>
> I knew that that could happen. I was under the impression
> it was only supposed to happen when running in full screen
> mode under Linux. The problem is that under certain
> conditions (that is, full screen mode under Linux) the
> virtual hardware cursor is really a software cursor,
> so you have to turn it off before drawing. I was hoping
> that VMware would add real hardware cursor support and
> I could avoid this.
After some tests, I have found I can reproduce the bug only in full
screen mode.
>
> What if you kill off the clock and the stats windows,
> so that nothing could possibly be drawing on the display?
> Then does the mouse still have problems? If so, it's probably
Yes. I still have problems if I kill the stats and clock. When in full
screen mode the mouse leaves a trace when I create a new window. Also
it leaves a trace on the little green window with new resize etc. which
appears when you click the right button on rio.
> just a bug of mine rather than this pseudo-hardware cursor
> problem.
>
I only happens on full screen mode, so it may be the software cursor problem...
--
Saludos,
Gorka
"Curiosity sKilled the cat"
next prev parent reply other threads:[~2002-05-06 1:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-05 23:24 Russ Cox
2002-05-05 23:33 ` arisawa
2002-05-05 23:39 ` [9fans] u9fs arisawa
2002-05-06 1:42 ` paurea [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-04 20:53 [9fans] Bug Report David
2005-05-04 21:01 ` Russ Cox
2005-05-04 21:05 ` andrey mirtchovski
2002-05-08 15:11 [9fans] Bug report Russ Cox
2002-05-06 20:12 Russ Cox
2002-05-06 20:05 markp
2002-05-06 18:14 Russ Cox
2002-05-06 20:23 ` Mike Haertel
2002-05-06 22:25 ` paurea
2002-05-08 2:52 ` Paul O'Donnell
2002-05-06 17:57 Russ Cox
2002-05-06 18:03 ` Mike Haertel
2002-05-06 17:39 markp
2002-05-06 2:25 Russ Cox
2002-05-05 23:18 paurea
2002-05-06 12:54 ` Paul O'Donnell
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=15573.57238.155353.295574@nanonic.hilbert.space \
--to=paurea@gsyc.escet.urjc.es \
--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).