[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:	DECmcc user notes file. Does not replace IPMT.
Notice:	Use IPMT for problems. Newsletter location in note 6187
Moderator:	TAEC::BEROUD

Created:	Mon Aug 21 1989
Last Modified:	Wed Jun 04 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	6497
Total number of notes:	27359

5564.0. "Notify events and Screen Saver !" by COPCLU::OVESEN (Michael Ovesen @DMO 857-2739) Sat Sep 04 1993 19:30

    
    Our customer has a VAX 4000-100 wich has screen saver turned on,
    to save the monitor.
    
    When the screen saver has turned off the screen and there is a notify
    comming the screen is still turned off. Is there a way to make sure
    that the screen is turned on when there is message to the screen. 
    
    It looks very simple to change this. 
    
    The notify routine should performed the following call.
    
    stat = XForceScreenSaver(NotifyDisplay, ScreenSaverReset);

    before it update the notify window.
    
    Is there a docmented or undocumented way to get the screen turned on
    when there is a notify event ?

T.R	Title	User	Personal Name	Date	Lines
5564.1	not possible in V1.3, maybe a work-around?	SISE::DITMARS	Pete	`Tue Sep 07 1993 15:09`	17
	The code doesn't presently do this. I wish I had known about the XForce... stuff before. Please QAR this, as it would be simple to add to a maintenance release (if there is another). If it's an alarm that is firing, and the alarm is already running a procedure, it might be worth investigating having the customer's alarm fired procedure invoking an executable which does the XForceScreenSaver call. With a little care to minimize the overhead involved, e.g. setting a logical with the timestamp of the last Force and checking it before doing another Force, this might work quite acceptably. If it's not an alarm rule, i.e. it's only an event, then you might define an alarm rule on those events which does the same thing i.e. listens for the event and turns off the screen saver in anticipation of the notification coming up.
5564.2	Wrong thing to do.	RACER::dave	Ahh, but fortunately, I have the key to escape reality.	`Wed Sep 08 1993 11:21`	9
	Wait, please dont just add it..... This is exactly the wrong thing to do for many people. Almost every system I have ever used does not look at output as resetting the screensaver. Input only. If you want to make the change, make it selectable, not just one way or the other. (Even use a bit in MCC_IM_PM_LOG if you need to....)
5564.3		SISE::DITMARS	Pete	`Thu Sep 09 1993 14:39`	1
	Of course it would be customizable behavior.
5564.4	Great. When can we expect this maintenance release ?	COPCLU::OVESEN	Michael Ovesen @DMO 857-2739	`Thu Sep 16 1993 08:31`	8
	Thank you for your answers. I agree this should a customizable behavior. Our customer is lookeing forward to this feature. When can we expect a maintenance release with this option ?
5564.5	did you submit a bug report?	TOOK::CALLANDER		`Fri Sep 17 1993 14:39`	6
	before you can wait on a maintenance release you must first have them submit a qar (cld) on this so that the fix gets in the queue. Please remember this is just a notes file and that since this is a released product a formal bug report is needed to help assure a fix in the next maintenance release.
5564.6	SPR is comming	COPCLU::OVESEN	Michael Ovesen @DMO 857-2739	`Tue Sep 21 1993 18:13`	1
	I agree. We will submit a SPR.