feat: thinner border (4 px) and serial logging on border / recovery events
- BORDER_THICKNESS_PX: 16 -> 4. Hardware-tested at 4 px on both yellow and red; yellow appears slightly thicker due to the irradiation illusion (perception, not a rendering issue) — not compensating per color absent an explicit request. - Add Serial.println at every state transition that touches the err_border lifecycle: schema migration firing, sync-fail else branch (with HTTP code, distinguishing border vs full-fill fallback), 304 recovery (with which flags triggered it), and recovery completion / abort. Lets us trace why a frame is or isn't showing a border via pio device monitor without needing to instrument anew each time. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
+1
-1
@@ -38,7 +38,7 @@
|
||||
#define NVS_SCHEMA_VERSION 1
|
||||
|
||||
// Width of the sync-fail / no-WiFi border, in pixels.
|
||||
#define BORDER_THICKNESS_PX 16
|
||||
#define BORDER_THICKNESS_PX 4
|
||||
|
||||
// ── Network ──────────────────────────────────────────────────────────────────
|
||||
#define APP_BASE_URL "https://pictureframe.edholm.me"
|
||||
|
||||
Reference in New Issue
Block a user