We are currently migrating Bugzilla to GitHub issues.
Any changes made to the bug tracker now will be lost, so please do not post new bugs or make changes to them.
When we're done, all bug URLs will redirect to their equivalent location on the new bug tracker.

In SDL 1.2, we defaulted to disabling the screen saver while there was an SDL Window on the screen, and there was a environment variable hack to make SDL _not_ disable the screen saver.

The gist was most things using SDL are video games or media players, and they don't want the screensaver to interfere. The rare exception that wants to work like a normal desktop app, like TuxPaint, could explicitly ask SDL to allow the screen saver.

In 2.0, we have a formal API for the screen saver, but it defaults to allowing it to function.

I think this should work like 1.2 did. Otherwise, games that are interacted with through joysticks exclusively, or video players that we watch without touching, will get blocked by the screen saver popping up every few minutes, because the default behavior of SDL has changed to something unexpected.

--ryan.