Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!mips!smsc.sony.com!dce
From: dce@smsc.sony.com (David Elliott)
Newsgroups: comp.windows.x
Subject: Re: xswarm 2.0 blanker weirdness
Message-ID: <1991Jan16.160205.19684@smsc.sony.com>
Date: 16 Jan 91 16:02:05 GMT
References: <1991Jan15.042140.2591@unixg.ubc.ca>
Organization: Sony Microsystems Corp, San Jose, CA
Lines: 28

In article <1991Jan15.042140.2591@unixg.ubc.ca> lindholm@greve.ucs.ubc.ca (George Lindholm) writes:
>I'm seeing some pretty weird behaviour by the xswarm blanking code. Several
>times the blanker has kicked in a couple of seconds after I had just used
>the keyboard and it was no-where near 300 seconds since the previous time.
>I have also seen the blanking cover the left half of the screen only !???
>What is going on here???

Oh, it get's better. ;-)  I tried using it with tvtwm and here's
what happened:

	1. The screen "blanked" after 20 seconds (like I told it to),
	   but all the sticky windows stayed visible.

	2. Mouse and keyboard events didn't cause the screen saver
	   to go away, though I could get keyboard events to tvtwm
	   to get me to another part of the virtual screen.

	3. Once in another part of the virtual screen, I could see
	   the windows there, but couldn't get focus.

	4. From my X terminal, I killed xswarm, and the screen went
	   completely dark.  Nothing I did could get the screen to come
	   back.

	5. So, I killed my X server, and logged in again from xdm.

It was a good idea, but I still think that the server extension
for screen savers is the only way to get this to work right.