fix(worldclock): keep seconds quiet for TalkBack and apart from the defaults

The time each row and the home readout give TalkBack stays at minute
precision, and the ticking text is kept out of the tree, so a focused
row is not re-read every second. The row's time is capped in width and
shrinks to fit, so a large font scale cannot crowd out the city name.

The setting is its own SettingsPrefs flow rather than a ClockDefaults
field, so flipping it re-emits nothing alarms and timers watch. The
clock-change receiver sits outside the flatMapLatest and restarts the
tick, registering once per subscription and re-measuring the wait
against the clock as it now reads.
This commit is contained in:
makiolaj committed 2026-10-21 19:07:19 +02:00
1 parent a4cec23e5c
commit 65c86af313
21 files changed
+138 -53

No files matched your search

+2 -1
View File
@@ -145,7 +145,8 @@ Field names mirror `ClockPrefs`'/`SettingsPrefs`' own on-disk keys. Older
files may also carry `default_timer_duration_millis`, from a default timer
length setting that has since been removed; it is ignored on import like any
other unknown field. Files from before `world_clock_show_seconds` existed
import with it off, its default. Every
import with it off, its default. It travels with the settings but is not a
clock default: nothing an alarm or timer inherits depends on it. Every
numeric/duration value is clamped on *apply* using the same ranges and encoding
as the existing preference setters, never on parse.