fix(alarms): apply silence-after mid-ring and close missed one-shots
Review fixes for the silence-after setting. Changing the alarm's silence-after now re-measures a ring in progress at once, through AlarmEngine.onSilenceAfterChanged: past the new window it closes as missed, inside it the backstop moves. onAutoSilence also re-arms instead of closing a ring that is still inside the current window, so a backstop armed for a shorter window cannot end a ring early. A cycle the resolver closes as missed (a ring past its window, or a snooze that never fired) now disables a one-shot alarm, as the engine's own close does. A short window made that path much easier to reach, and the alarm was being armed for the same time the next day. A late snooze is kept for the window or ten minutes, whichever is longer, so a short window never makes a promised snooze easier to lose than in v1. A timer that has gone quiet stays quiet when the setting is raised: the lapsed anchor moves back past the hard stop. The timer's heads-up is now keyed to the session anchor rather than the window's end, so editing the setting mid-ring no longer counts as a new session and alerts again. A negative stored value now reads as the default instead of Never. The picker offers a stored value that matches no choice, and the wake-lock timeout is one shared constant. Refs #17
This commit is contained in:
1 parent
412e54db09
commit
1c323d5b4c
20 files changed
+397
-88
No files matched your search
+2
-1
@@ -151,7 +151,8 @@ other unknown field.
|
||||
are how long a ringing alarm or a finished timer keeps going before it stops on
|
||||
its own: whole minutes, with `0` meaning "Never" (which still stops after an
|
||||
hour). A file without them, from before the setting existed, imports as `10`,
|
||||
the value it was made with. Out-of-range values clamp to 0..60.
|
||||
the value it was made with. A value over 60 reads as 60 (which is what Never
|
||||
rings for anyway); a negative one reads as the default, 10.
|
||||
|
||||
Every numeric/duration value is clamped on *apply* using the same ranges and encoding
|
||||
as the existing preference setters, never on parse.
|
||||
|
||||
Reference in new issue
Block a user