Prevent timer from lagging behind

[twinkelmann]

Implemented the timer with setTimeout instead of setInterval to control the delay between each calls and prevent accumulation of lag.

Instead of accumulating ~2 ms of lag on each interval, this method will keep the lag in check on the long run.
It cannot accumulate as each interval is calculated with the current lag in mind.

This change partially addresses #32 (window in background might still cause issues, so I can't say this alone will fix it).

[Splode]

Great strategy. I think this will definitely help the timer's accuracy.

Thanks for the awesome contribution! 💯

[twinkelmann]

Glad to contribute 👍

[NeonArray]

I'm curious if using performance.now() would be more accurate than Date? I'd be interested to see some performance benchmarks as well as some sort of verifying unit tests. I'm just wondering which method is more accurate for a timer in this context, and without tests it's all just sort of assumption and conjecture.

Not saying it would make a difference here necessarily. I just happened to be reading about timers the other day and thought I'd throw this information at you guys for your consideration.

I'd also still consider using Electrons built in API's for timing as they seem a bit more "bullet proof."

• When Milliseconds Are Not Enough
• Stack Overflow Question

Anyway, happy coding!