On 09/22/2010 09:36 AM, Johan Vromans wrote: > Johan Vromans <jvrom...@squirrel.nl> writes: > >> So, how can an application find out whether the screen saver is active, >> or, more precisely, the screen is blanked? Can I do this using the Win32 >> core API? > > The other half of the problem is how to effectively disable responding > to clicks. One way I can think of is to check a global flag in each and > every event handler. Cumbersome, but doable. But maybe there's a better > way? Temporarily mapping a transparent window over the screen that > intercepts clicks?
Why don't you write a screen saver that does something like this?: Create a new window that covers the whole screen, then immediately start a "real" screen saver. Exit on the first click/keystroke recieved. Are Windows screen savers still plain .exe files? (they were the last time I tried. - which was on my old 486 with Windows 98 :D ) -- Steffen
