|
Post Reply
aok 2005-12-10 05:20
I'm currently using the Screen Saver Player as a work-around for getting a screensaver to display on my touchscreen (primary) monitor while watching a movie on my secondary (HDTV) monitor with Zoomplayer which otherwise prevents screensavers from working.
However, unless I'm missing something, the Screen Saver Player doesn't operate like a typical screensaver in that touching the touchscreen (or moving the mouse) won't exit it. I've create a work-around for the work-around in which the "Stop" button on my remote also sends a "Kill Process" to the Screen Saver Player but I'm curious how otherwise I might get SSP to exit?
|
Christian Studer 2005-12-10 08:59
If the screen saver player is in fullscreen mode, you can close it by pressing ALT+F4.
Killing the process isn't ideal, because the screen saver started by the screen saver player will continue running.
If the software for the remote supports it, you could send ALT+F4 to the screen saver player to close it.
Christian Studer - www.realtimesoft.com
|
aok 2005-12-10 09:49
Hmmm... that isn't proving to be the case. Killing the process also kills the screensaver, or at least it appears to (screensaver stops and screen beneath it is displayed). I'll need to check my Task Manager next time to make sure the screensaver isn't lingering in the background somehow...
Alt+F4 isn't really ideal as I can't send it specifically to the screensaver, and it's liable to exit the movie I'm watching instead (I guess it depends where the mouse is at that point, which is too much trouble to determine).
FWIW, I'm using a USB-UIRT combined with Xlobby to interpret and re-route my remote signals...
|
aok 2005-12-10 10:40
You were right, of course. Instances of the screen saver (.scr) were stacking up in the Task Manager, though not actually doing anything or apparently eating up any memory. The solution was to have the Stop Playback button not only kill the Screen Saver Player process, but also the .scr as well...
Thanks for your time and feedback.
|
Post Reply
|
