2) Yes, but you need to be handling the windows message pump yourself, as Budman already mentioned. You need to monitor for WM_SYSCOMMAND and if you get one, check if it's the SC_SCREENSAVE message. When this happens, this basically Windows saying "Hey, I think I'm gonna start the screensaver now. Do you mind?" If you return True from your WndProc, you're saying you don't mind. If you mind, you return False.
I guess BlitzMax needs a DisableScreensaver() and EnableScreensaver() pair of functions, because I don't think you can do this without creating your own window and managing it, which I'm guessing would be incompatible with your framework, and if Mark just sets BMax to tell the screensaver not to start always, he'll get complaints from people who don't want their applications stopping the screensaver.
Personally, I think it's a bad practice to disable the screensaver in an application, but a bad practice *not* to disable it in a game. I hate when games don't disable the screensaver. Only on the rare occasion I've reformatted and not completely disabled it, of course, but still. Don't like it.
I guess BlitzMax needs a DisableScreensaver() and EnableScreensaver() pair of functions, because I don't think you can do this without creating your own window and managing it, which I'm guessing would be incompatible with your framework, and if Mark just sets BMax to tell the screensaver not to start always, he'll get complaints from people who don't want their applications stopping the screensaver.
Personally, I think it's a bad practice to disable the screensaver in an application, but a bad practice *not* to disable it in a game. I hate when games don't disable the screensaver. Only on the rare occasion I've reformatted and not completely disabled it, of course, but still. Don't like it.