it disables itself even when no key is pressed, for example when another app brings up a new window or popup.

Also, it would be especially cool for such a screensaver to allow different dimming settings for day and night - dimming to the same level makes it now hard to recognize the dimmed screen content at day when it's perfectly set for night use.

I think that the response to both posts could be a script that you set as screensaver, and that can do all you mentioned.You can copy powerdimmer's executable twice, each one with different options (for day and night), and the script would run each of them.As for powerdimmer not recognizing keyboard events, it has never happened to me...Having 2 different screensavers is quite easy if you have a script that controls them, it would activate powerdimmer first, then send a key for powerdimmer to be closed, and would then launch the other screensaver.

I think that the response to both posts could be a script that you set as screensaver, and that can do all you mentioned.You can copy powerdimmer's executable twice, each one with different options (for day and night), and the script would run each of them.

Thanks, that got me thinking... one surely could do that OR one could code an AHK script based on A_TimeIdlePhysical that would just start one of the predefined powerdimmer copies based on the current time!

@skrommel: thanks! How do you feel about adding an option to just turn the monitor off/enter low-energy-mode later instead of starting another another screensaver?

[Edit]:There's a bug: I did set the day settings, but the night settings are being used.

Some more suggestions:- add an "exclude list" for buttons that will NOT disable the screensaver! That way one would be able to use Winamp's Global hotkeys and other stuff without turning off the dimming! I'd love that - you could also add options whether it should disable itself on keyboard and mouse activity or on one of those two only. I'm using a Miranda plugin which has such a feature (did I tell you I love being able to customize stuff? )

Please upgrade DimSaver to v1.3! And remember to remove the existing ini-file.

I've very sorry for last night's very buggy version. I had no multimonitor to test it on, the day and night settings weren't working (still don't know why), the values got swapped (so check the options window), the mousemove, -clicks and keys settings weren't saved, the list goes on. So take my advise and get to bed early - there's nothing like a good night's sleep!

report on 1.3:multimon works (well done)dimsaver uses 89% of the cpu while its running - OUCH! if it uses this much even after screen is dimmed completely then this would be a show stopper for me since i don't want to have my cpu hitting 90% cpu overnight for no reason.the dimming seems MUCH MUCH slower, even at fastest speed, than before.it seems to Undim (and exit) after it finishes dimming! (ie 60 seconds) - i dont think this is intended

Mouser, DimSave creates a window coverting all monitors, and changes the transparency. It's Autohotkey's transparency function that's so CPU intensive, and the bigger the window, the slower it is. I could make it skip every other transparency, but it would still use a lot of CPU. But afterwards it shold be fine. What delay have you entered in the settings dialog? Have you selected a screensaver to run next? There could be a bug in there...

brotherS, I think your problems with the WinActivate function is also related to the transparency, by always staying active. And to turn off the monitor afterwards, install my MonitorOffSaver. About the hotkeys, I'm not shure how to detect them.