![]() You've written your whole screensaver in a Windows Form. ![]() Debugging screensavers can be a nightmare when they're running in full screen.You decide you want to use a timer to avoid pinning the CPU, maybe, but on Windows 9x/2K/XP, it doesn't provide enough precision to run a screensaver at even 30 frames per second.Behavior in response to mouse and keyboard input is inconsistent some screensavers don't snap out until you actually click on the mouse.Īnd here are some of the troubles for developers:.Some screensavers use the "game loop" design, crippling background applications and causing a lot of modern CPUs to overheat.There's often no Settings box, not even a really simple one.Previews often don't show up properly in the Display Properties dialog box.Multiple monitor support is often flakey, especially when monitors aren't of equal sizes.Here are some of the most bothersome ones for users: But there's a bunch of quirks along the way. Screensavers seem easy enough to set up on Windows, all you have to do is to rename an. What's not so nice about them is the way a lot of them behave, and the way they have to be written. They don't serve much of a practical purpose anymore now that monitors don't "burn" images onto the screen, but they do turn your computer into a pretty decoration when you're not around, and it's a lot more healthy to be staring at screensavers all day than to be hooked on MMORPGs.
0 Comments
Leave a Reply. |