For this particular use case (any activity in the last 10m), resetting the history is not a problem because BTN3 reset is activity and clearing the history does lead to the same behavior (assuming activity by default). However, this is usually an exception rather than the norm.
Regarding E.on('kill', ...: power off proofness in this case is not desirable ;)
Thanks again for the confirmation and detailed response!
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.
Thank you for the details, I feared as much. The use case is:
Every 30s check if the watch is in power save mode. Remember this to keep track of recent activity and act accordingly.
Related issues:
https://github.com/espruino/BangleApps/issues/1923
https://github.com/espruino/Espruino/issues/2308
For this particular use case (any activity in the last 10m), resetting the history is not a problem because BTN3 reset is activity and clearing the history does lead to the same behavior (assuming activity by default). However, this is usually an exception rather than the norm.
Regarding
E.on('kill', ...
: power off proofness in this case is not desirable ;)Thanks again for the confirmation and detailed response!