I executed an infinite loop function via webIDE-console yesterday
Thanks! I just checked and it seems the short-press won't break out of executing JS. I've just pushed some changes to the latest cutting edge firmwares, so if you try those now then you can hold the home button to get out of infinite loops.
While it won't fix the clock updating I'd be really interested to see if when the Bangle breaks, it now allows you to go back to the menu with a long-press without totally resetting the watch. If that's the case it'll just be some JS on the watch that was in an infinite loop.
Just experienced the frozen watch again:
Thanks - Is that at all reproducible? Interestingly when you connect, GB sends a Ctrl-C character which would break out of executing code, so if this were some JavaScript code on the watch that's actually locking up, it would make sense.
I feel like we're getting there... If this does allow a short-press to reset the watch then I can add something to the firmware that detects if some JS code has been busy for more than 60 sec, and if so breaks out of it with a stack trace. Then, we can not only stop this from happening again, but can also figure out what code is causing the problem.
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.
Thanks! I just checked and it seems the short-press won't break out of executing JS. I've just pushed some changes to the latest cutting edge firmwares, so if you try those now then you can hold the home button to get out of infinite loops.
While it won't fix the clock updating I'd be really interested to see if when the Bangle breaks, it now allows you to go back to the menu with a long-press without totally resetting the watch. If that's the case it'll just be some JS on the watch that was in an infinite loop.
Thanks - Is that at all reproducible? Interestingly when you connect, GB sends a Ctrl-C character which would break out of executing code, so if this were some JavaScript code on the watch that's actually locking up, it would make sense.
I feel like we're getting there... If this does allow a short-press to reset the watch then I can add something to the firmware that detects if some JS code has been busy for more than 60 sec, and if so breaks out of it with a stack trace. Then, we can not only stop this from happening again, but can also figure out what code is causing the problem.