[6293] in Athena Bugs
x11 server/dix/window.c:SaveScreens
daemon@ATHENA.MIT.EDU (Ken Raeburn)
Mon Oct 29 00:30:58 1990
Date: Mon, 29 Oct 90 00:30:40 -0500
From: Ken Raeburn <Raeburn@MIT.Edu>
To: bugs@ATHENA.MIT.EDU
Cc: marc@ATHENA.MIT.EDU
I believe (and Marc agrees) that at least one (probably all?) of the
calls to ...->SaveScreen should have the argument `on' changed to
`what'.
The current behavior is that the SaveScreen routine gets called with
SCREEN_SAVER_ON, SCREEN_SAVER_OFF, or SCREEN_SAVER_FORCER. The last
results from client requests. The device-dependent routine to control
video blanking does not know, when SCREEN_SAVER_FORCER is passed,
whether the video signal should be enabled or disabled.
The result is that the code I sent in a while ago (real video blanking
for RT and VAX/SM) turns video on and off over time, if some program
(like zwgc) resets the screen saver occasionally.
The SaveScreen routine should be called with SCREEN_SAVER_ON or
SCREEN_SAVER_OFF, depending on the current state; SCREEN_SAVER_FORCER
does not provide enough information. SaveScreens has enough
information available to determine what that value should be.
-- Ken
