Twenties: refactor to use the scheduling library instead of its own timeouts#4231
Twenties: refactor to use the scheduling library instead of its own timeouts#4231thyttan wants to merge 29 commits into
Conversation
|
Thanks for working on that! For curiosity, how are you testing the code in the IDE? On my side, it doesn't read the file from storage correctly, and if I upload the unminified javascript (either to RAM or to storage, replacing the original), I have an error that |
I get those as well, but it works anyways. When the code runs on the watch it will find the The |
Yes I think that makes sense. Gordon and I discussed it some in #4217
I did that before. I prefer to avoid it. But maybe it makes sense. |
I think if we can hide it with
Well, it's only a warning. It's hard because in most non-Bangle.js devices it's pretty helpful. It's a bit of a pain to work around, but in the dev IDE (https://espruino.github.io/EspruinoWebIDE/) I've just added a change that means it'll now search |
…idden"." This reverts commit 5b8c6e7.
by setting `.group` = "Hidden"
setting an alarm at a time that had already occurred today would fire immediately instead of be scheduled for tomorrow.
(I think that was the problem at least.)
Didn't help fully. May try again. Added first in 75999de
So user is alerted that this is not a normal alarm.
Work in progress.
Try the current iteration at: https://thyttan.github.io/BangleApps/?id=twenties