From the win32 sdk
Once a screen saver is chosen, Windows monitors keystrokes and mouse movements, starting the screen saver after a period of inactivity. However, Windows does not start the screen saver if any of the following conditions exist:
· The active application is not a Windows-based application.
· A computer-based training (CBT) window is present.
· The active application receives the WM_SYSCOMMAND message with wParam set to the SC_SCREENSAVE value, but does not pass the message to the DefWindowProc function.
There doesn't appear to be a simple API command that just detects if the screensaver has been activated.
But you might be able to intecept the WM_SYSCOMMAND in some way, this would require more investigation however.
Once a screen saver is chosen, Windows monitors keystrokes and mouse movements, starting the screen saver after a period of inactivity. However, Windows does not start the screen saver if any of the following conditions exist:
· The active application is not a Windows-based application.
· A computer-based training (CBT) window is present.
· The active application receives the WM_SYSCOMMAND message with wParam set to the SC_SCREENSAVE value, but does not pass the message to the DefWindowProc function.
There doesn't appear to be a simple API command that just detects if the screensaver has been activated.
But you might be able to intecept the WM_SYSCOMMAND in some way, this would require more investigation however.