Best practices for dealing with screen savers

Hi!

I've made a script that exports a bunch of files. However, after a while the screen saver goes on and causes problems when the script uses window conditions etc.

The obvious fix would be to turn off the screen saver, but I know myself well enough, so I will forget to turn it back on - and then, worst case there is the whole security thing.

I was thinking maybe I could simulate activitity while the macro is running to prevent the screen saver from starting. I could have the script hit keys or move the mouse. The latter is the better option as hitting keys could cause new problems. Not sure if it would count as activity if it's generated by KM instead of physically touching the mouse.

Any thoughts?

How about getting your macro to disable/enable the screensaver at start/end?

Here's a link to a topic that might help you Is there a way to set Screen Saver time to Never by Keyboard Maestro? - #3 by Nige_S

2 Likes

Thanks so much, that's a pretty good solution!

My first thought was that if I set it to "Never", and I cancel the macro, I would not remember to enable it again. But I think I can get by if set to 30 minutes - which feels just a little safer :slight_smile:

1 Like

Well, depending on how you "cancel" your macro, you could still construct it so that it does some tidying up (viz. enable the screen saver) before quitting. But if you're OK with the approach you mentioned that would be OK too :grinning: