You are reading a single comment by @Robin and its replies.
Click here to read the full conversation.
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
@Robin
Thanks @maze1980, having another view is helpful.
With the comment "I'd say it should look like" sounds like it hasn't been tested, which is okay don't get me wrong, any and all contributions are helping. That code block is pretty much what is being done and implemented right now based on Gordon's #8 snippets.
As I pointed out in #28 from an observation you pointed out earlier in this thread, setTimeout and setInterval 'actual' execution time is getting in the way of the setWatch() read. Too much to detail right now, but on the horizon.
Don't want #28 to get buried here with other updates:
Fr #28
What is the command or method to reveal if any setIntervals are running in memory, despite the attempt to stop them with clearInterval?