summaryrefslogtreecommitdiffstats
path: root/movement/movement.c
diff options
context:
space:
mode:
authorJoey Castillo <jose.castillo@gmail.com>2021-10-20 10:36:55 -0400
committerJoey Castillo <jose.castillo@gmail.com>2021-10-20 10:36:55 -0400
commit1020dd78981e0d4b4f20399aa5e76ea7d37beec6 (patch)
treed4e5a4118ed9ada934dcdde2b6afd46970e9b3c2 /movement/movement.c
parent148a47f76a457514c0571345d59c2179842cd30d (diff)
downloadSensor-Watch-1020dd78981e0d4b4f20399aa5e76ea7d37beec6.tar.gz
Sensor-Watch-1020dd78981e0d4b4f20399aa5e76ea7d37beec6.tar.bz2
Sensor-Watch-1020dd78981e0d4b4f20399aa5e76ea7d37beec6.zip
movement: fix preferences glitch, add some notes
Diffstat (limited to 'movement/movement.c')
-rw-r--r--movement/movement.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/movement/movement.c b/movement/movement.c
index a95501a4..df3cbf0b 100644
--- a/movement/movement.c
+++ b/movement/movement.c
@@ -209,7 +209,11 @@ void cb_tick() {
event.event_type = EVENT_TICK;
watch_date_time date_time = watch_rtc_get_date_time();
if (date_time.unit.second != movement_state.last_second) {
+ // TODO: since we time the LED with the 1 Hz tick, the actual time lit can vary depending on whether the
+ // user hit it just before or just after a tick. If we time this with the system tick we can do better.
if (movement_state.light_ticks) movement_state.light_ticks--;
+
+ // TODO: can we consolidate these two ticks?
if (movement_state.settings.bit.le_interval && movement_state.le_mode_ticks > 0) movement_state.le_mode_ticks--;
if (movement_state.timeout_ticks > 0) movement_state.timeout_ticks--;