From 5aa9a46dcfdc0d012483bf1331797fb760908fb5 Mon Sep 17 00:00:00 2001 From: "Rich O." Date: Sun, 1 Nov 2026 16:11:54 -0500 Subject: [PATCH] progress: clock fixed end to end; mentions and segments verified on the Neo --- docs/progress.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/progress.md b/docs/progress.md index 7525514..f4a4bbb 100644 --- a/docs/progress.md +++ b/docs/progress.md @@ -72,3 +72,5 @@ - MeshTerm-style UI built: generated 4x6 font (PilRC's FONT compiler writes a corrupt NFNT, so gen_font.py writes it), rowlist, text layout (host-tested), message store and sync, Home/Conversation/Contacts/Node screens. Font verified readable on the Neo. - Transcript wrapped after ~4 characters on the Visor: prc-tools puts `const` data in the code section, but another file reaching an `extern const` table addresses it A5-relative as data, so it read garbage widths. Shared tables (font widths, presets) are now non-const, set in their generators. Host tests can't catch this. Rule: never share an `extern const` table across files in palm-client. - Times were wrong: Palm OS 3.5's clock is local time with no zone, and it was used as UTC (and the Visor hadn't moved off DST). That made contact ages read 'now', and clock sync pushed a wrong time into the radio, which can only move forward. Now everything stored and sent is UTC via a UTC-offset app preference (Settings), the display converts back, and names are converted from UTF-8. +- Clock saga, resolved: the Neo's prefMinutesWestOfGMT was 1140 (19 h), so the default UTC offset was nonsense. The Visor's date was Oct 31 2026, then mistyped as Oct 1 2027, and each was copied into the radio, whose clock only moves forward. MeshCore restores its clock at boot from the newest contact "lastmod", so a contact heard during the 2027 window (TGNAB-01) kept bringing 2027 back. Fixed by rewriting that contact's lastmod (CMD_ADD_UPDATE_CONTACT with the optional last_mod field) and rebooting. The app now ignores system zones past +-14 h, only corrects a set radio clock by under 7 days (otherwise Node shows MISMATCH), and shows dates on the Node clock line. Radio within 7 s of real UTC. +- Mentions draw as chips and tap-to-reply works on the Neo. Two code segments verified on the device.