Closed wjhrdy closed 1 year ago
it seems like something in the js is calling the setinterval function and that is making it fail looking at the stack trace.
I finally put it on my watch and it is not crashing. yay
This is no longer a draft.
This is SO MONUMENTALLY COOL! My one desire would be for it to read the settings and display a 12-hour clock when the wearer has that preference set, but I'm not going to let that block merging this insanely cool watch face.
As for low energy mode, I guess it could fall back to just displaying the time as normal, but again, I think that can be handled in a separate PR.
Thanks so much for making this!!
This is a recreation of the Wyoscan watch, which was a $175 watch in 2014. It was an f-91w pcb replacement.
https://github.com/joeycastillo/Sensor-Watch/assets/1795778/e07f0ed1-e328-4337-a654-fa1ee65d883f
Here is more information on it: https://artmetropole.com/shop/11460
a demo of what it looks like: https://www.o-r-g.com/apps/wyoscan
8 frames per number * 6 numbers + the trailing 16 frames = 64 frames at 32 frames per second, this is a 2-second cycle time or 0.5 Hz.
It is giving me a stack overflow after about 2.5 cycles of the time display in the emulator but it works fine on the watch.
I'd like to make something for the low energy mode, but I haven't thought about how that might work, right now it just freezes in low energy mode until you press the 12-24HR button.