nanogui: Thread: screensaver

Forgive me if this was covered already,

I have a industrial computer, it uses a plasma display to handle extreme
temperature ranges (120DegF to -15DegF).  Therefore it needs to have the
screen blanked after a bit of time to avoid burn-in.  Is there anything
built into nano-X yet that supports calling a screensaver? or should I just
have an app running that after not seeing any mouse events for X amount of
time to take over the entire screen and fill it with #000000 as a color.

This really isn't a project for really useful purposes, this is a 386
computer that is in a sealed nema-4 case with an Infrared touchscreen, it
can withstand extreme temperatures and being hosed down and I thought what a
perfect control panel for my hottub! (I know real-bad overkill!)

Thanks all.
 

Tim,

Take a look at the GrSetScreenSaverTimeout() function:

http://home.twcny.rr.com/embedded/microwin/nxapi/nxapi_GrSetScreenSaverTimeout.html

Gary James
####@####.####
http://home.twcny.rr.com/embedded/




From:           	"Gray, Tim" ####@####.####
To:             	####@####.####
Date sent:      	Wed, 3 Oct 2001 06:14:26 -0600
Subject:        	[nanogui] screensaver

> Forgive me if this was covered already,
> 
> I have a industrial computer, it uses a plasma display to handle extreme
> temperature ranges (120DegF to -15DegF).  Therefore it needs to have the
> screen blanked after a bit of time to avoid burn-in.  Is there anything
> built into nano-X yet that supports calling a screensaver? or should I just
> have an app running that after not seeing any mouse events for X amount of
> time to take over the entire screen and fill it with #000000 as a color.
> 
> This really isn't a project for really useful purposes, this is a 386
> computer that is in a sealed nema-4 case with an Infrared touchscreen, it
> can withstand extreme temperatures and being hosed down and I thought what a
> perfect control panel for my hottub! (I know real-bad overkill!)
> 
> Thanks all.
>  
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: ####@####.####
> For additional commands, e-mail: ####@####.####
> 
> 



--
Gary A James, Critical Link, LLC         
Voice:  315.425.4045 x218  
Fax:    315.425.4048    
E-Mail: ####@####.####
WEB:    http://www.criticallink.com

Hi, Greg,

With Nano-X, currently root window always gets the keyboard focus after
screen saver is deactivated, thus make the modal child window modeless,
is this a known bug or by design? 

how can I make a modal modal child window stay modal after a screen
saver cycle?

Thanks,

/Michael.

On 04/10/05 09:32 -0500, Michael Gao wrote:
> Hi, Greg,
> 
> With Nano-X, currently root window always gets the keyboard focus after
> screen saver is deactivated, thus make the modal child window modeless,
> is this a known bug or by design? 

I'm gong to go ahead and call that a bug.  If you have a modal child, it
should retain the focus through a screensaver event.

Jordan

-- 
Jordan Crouse
Senior Linux Engineer
AMD - Personal Connectivity Solutions Group
<www.amd.com/embeddedprocessors>

On 4 Oct 2005, at 16:31, Jordan Crouse wrote:
> On 04/10/05 09:32 -0500, Michael Gao wrote:
>> With Nano-X, currently root window always gets the keyboard focus  
>> after
>> screen saver is deactivated, thus make the modal child window  
>> modeless,
>> is this a known bug or by design?
> I'm gong to go ahead and call that a bug.  If you have a modal  
> child, it
> should retain the focus through a screensaver event.

The screensaver needs the keyboard focus so that it can listen for a  
keyboard event on which to exit, then when it exits, the server  
doesn't remember which window had the focus before the screensaver  
did, so it defaults to giving it to the root window. I think it  
should be possible to fix this by having nsaver do a GrGetFocus() on  
startup to find out the previous owner of the focus, then do a  
GrSetFocus() on exit to restore it.

-- 
------------ Alex Holden - http://www.alexholden.net/ ------------
If it doesn't work, you're not hitting it with a big enough hammer