When you program something that should happen when the user is five+ minutes idle with the focus on app and you have to test it. Good having a couch in the office.

How about debug settings that you can tweak to reduce that time during development ?

If it works after 30 seconds, it will work after 5+ minutes i guess.

@Grumm That would be a pretty surprising feature. Users hate and get confused by surprises.

@Oktokolo Well users will not see it. Since it is only for 'debugMode'.

That is a nice feature in Visual Studio. When compiling the release, users don't see all the print logs and other crap.

But it helps the devs to test features like this faster and go on with their work.

@Grumm sure. But i wanted it to test once in real life setup to see how it interferes with other longtime events.

@Grumm Sorry, i forgot to remove the @ nick as i decided that the original feature could be a bad idea.

@horus As long as it is during office hours, go sit in that couch with a gaming controller :D

@ostream That wouldn't work if the monotonic clock implementation in use isn't synced to the clock.

A better solution is having a system providing timer functionality as an injected dependency so you can replace it with a rigged version when testing.