From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15573.57238.155353.295574@nanonic.hilbert.space> From: paurea@gsyc.escet.urjc.es To: 9fans@cse.psu.edu Subject: Re: [9fans] Bug report In-Reply-To: <818a4b58332c9faa04a62c3ebaeb5250@plan9.bell-labs.com>:Russ Cox's message of 19:24:29 Sunday,5 May 2002 References: <818a4b58332c9faa04a62c3ebaeb5250@plan9.bell-labs.com> Date: Mon, 6 May 2002 03:42:46 +0200 Topicbox-Message-UUID: 892b5e6a-eaca-11e9-9e20-41e7f4b1d025 Russ Cox writes: > From: "Russ Cox" > 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"