 |
| How to start the screen saver and how to find whether the screen saver is active |
User rating: 0/10 (0 votes) | |
|
|
|
|
| Before you begin: |
|
Screen Saver can be started programmatically by calling SendMessage or PostMessage function.
See also:
Closing access to the Windows Desktop and to other applications
Using the SystemParametersInfo function
|
|
|
| |
| |
Members area. Log in to view this example. |
|
| |
|
|
|
|
|
|
User rating: 0/10 (0 votes) | |
| 1398 bytes
Created: 2001-11-22 21:03:15
Modified: 2008-11-03 15:26:13
Visits in 7 days: 79 |
|
|
|
| Listed functions: |
|
|
|
|
| My comment: |
|
Use HWnd of a form or of the Main FoxPro screen as the first parameter. With hWindow=HWND_BROADCAST, the message is posted to all top-level windows in the system, including disabled or invisible unowned windows, overlapped windows, and pop-up windows.
Initiated this way, the screen saver may not become password protected immediately, regardless of the setting in the Display Properties "On resume, password protect". It changes to protected status only after the Wait period expires. This is true for at least XP Home systems.
For the password protected screen saver, the system creates "WinSta0\Screen-saver" desktop and starts a process with "Screen Saver" window attached. So the application may judge about the state of the sreen server by finding out if this desktop exists.
Screen saver without password protection is running on "WinSta0\Default" desktop. It owns "Screen Saver" window that class is "WindowsScreenSaverClass". So this is another way of detecting whether a screen saver is active. |
|
|
| Word Index links for this example: |
|
|
|
|
|
| Translate this page: |
|
|
How to change display settings: screen resolution, screen refresh rate
