Most recent activity
-
I had no idea adding a date was a possibility. Not sure how I missed it, may have been the visual offset from "msg" that put it in the day of week section in my head. Possibly also carryover expectations from when I last looked the alarm app.
I have to dig into it but it should cover my use cases.
The only concern would be whether applications that don't handle dates may be confused.
-
As it stands the scheduling library is highly alarm focused.
Would it make sense to extend it to encompass the scheduling of events with absolute timestamps?
Potential benefits:
- Countdown timers would gain the ability to schedule more than 24 hours out and accurate negative time.
- Persistent stopwatches.
- Syncing of calendar events.
- Place for apps to push events such as sunrise and sunset.
- Countdown timers would gain the ability to schedule more than 24 hours out and accurate negative time.
-
Well, looks like most of the issue is me my dry fingers plus some touch screen imprecision. Tapping in place can produce a minor, but distinct spread which is enough to miss repeatedly given the size of the buttons.
That said, occasionally the touch event does not fire, in which case the prompt tends to not respond. Very rarely the prompt works but the touch event does not or the crosshair is drawn over a button with no response from the prompt.
EDIT: notably I have not had any trouble reliably hitting, e.g., buttons in the calculator app. I don't know if there's a UX difference with full screen applications prompting me to be more precise or something else.
-
I should have noticed that, sorry.
-
It happens very consistently at the very least with alarm app timer prompts and prompts triggered from the web IDE.
Video of uploading the prompt example code and having to settle for two fish: https://youtu.be/O4mDtftum5U
-
Are you actually having issues and you think that might be the cause?
Not that I'm aware of. I intend to make timer app that can run in the background so I was trying to understand understand what exactly the alarm app does and why it does.
As noted, I think alarm.js is only called when an alarm is due, and it is called with load(...) so everything else is removed at that point and it's just the boot.js code that is run.
Does that mean that the clearInterval effectively only applies until alarm.js is done? That certainly would make it very unlikely to impact pending timeouts... I may have been more confused about how often boot actually runs in that case.
Is there some distinction between boot.js and boot0.js that could lead to another load of alarm.js? Or is there some some special handling of all alarm.js files as hinted in the BangleApps Readme (although I couldn't really find any more on that) that may affect it?
I may be overthinking things...
Mine came off within days. Aggressive sweat is the likely cause in my case. Masking tape is doing the job for now but I'm considering superglue or something for long term.