GordonF
December 7th, 2003, 08:31 PM
Something to watch out for in v5.
If you leave KP running but you step away for some reason, usually the screen saver kicks in. Some of us, notably Win2K and XP users, have the screen saver also lock the keyboard (not necessarily for security reasons - I have a cat who likes to sleep on my keyboard and locking the computer saves my cat from pressing the Delete key.)
But when Win2K is locked, unlocking it causes the KP preview display to go grey with the word "default" in plain Windows text. KP promptly crashes afterward. I can send the drwstn32 log if you want it.
Some games do this too, but that's only because the games were badly coded for handing that. I have some OpenGL games that deal with it gracefully, and most DirectX stuff deals with it too.
If you leave KP running but you step away for some reason, usually the screen saver kicks in. Some of us, notably Win2K and XP users, have the screen saver also lock the keyboard (not necessarily for security reasons - I have a cat who likes to sleep on my keyboard and locking the computer saves my cat from pressing the Delete key.)
But when Win2K is locked, unlocking it causes the KP preview display to go grey with the word "default" in plain Windows text. KP promptly crashes afterward. I can send the drwstn32 log if you want it.
Some games do this too, but that's only because the games were badly coded for handing that. I have some OpenGL games that deal with it gracefully, and most DirectX stuff deals with it too.