3 Commits

Include renames

Author	SHA1	Message	Date
tfaour	42d7c09f97	Make the upcoming-photos queue length user-configurable ... Adds "Upcoming photos to show" to the config UI (queue_target_len, 5-50, default 20, replacing the hardcoded QUEUE_TARGET_LEN constant). Lowering it trims the queue immediately on next page load rather than waiting for enough advances to consume the excess naturally; raising it tops back up the same way, via a new photo_queue.sync_queue_length() called from GET /api/queue.	2026-07-19 01:03:05 -04:00
tfaour	de41b00210	Web UI: grid layout, drag-and-drop reorder, and "show next" for upcoming photos ... Replaces the up/down-button vertical list with a responsive photo grid (native HTML5 drag-and-drop between cards, reusing the existing POST /api/queue/reorder endpoint -- no new server route needed). Each card also gets a "Show next" button that jumps it straight to the front of the queue. Also bumps the queue lookahead from 10 to 24 photos (QUEUE_TARGET_LEN in photo_queue.py) now that the grid has room to show more at once.	2026-07-19 00:57:13 -04:00
tfaour	d395cf3bb9	Add two physical buttons: factory-reset and next-photo ... Factory-reset (GPIO3, hold 10s): clears stored WiFi/server config and restarts into provisioning -- the deliberate, USB-free replacement for the earlier reverted RST-based auto-reprovisioning idea. Next-photo (GPIO2, tap): wakes the device and forces the server to advance immediately via a new POST /frame/advance, instead of waiting for the refresh interval. Both buttons arm themselves as deep-sleep GPIO wakeup sources so a press is noticed promptly even while asleep. Also makes GET /frame/image side-effect-free: it now only advances once refresh_interval_s has elapsed since the current photo was set (tracked server-side), so a device reboot for any reason just redisplays the current photo instead of silently skipping ahead. The server maintains a small reorderable upcoming-photos queue, viewable and rearrangeable from the web UI.	2026-07-18 23:28:36 -04:00