Random refresh effect: choose which effects it picks from

The list is a new setting (hardware settings, also used by pages set to
Random); an empty list is refused. The ESP32 picks an effect per frame and
sends that, so the Nano needs no change. The power-on time after a frame now
follows the slowest effect on the list.

The settings record goes to version 8. Version 7 is a prefix of it, so it is
still read, and becomes version 8 with the next save.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
mangavalkandClaude Opus 5.5 committed 2026-11-04 02:41:41 +01:00
1 parent 8fcb17c395
commit 48e29096c0
12 files changed
+140 -21

No files matched your search

+3
View File
@@ -160,6 +160,9 @@ See README.md for the overview.
`web/web_ui.cpp` is the JSON API (endpoints listed in `web_ui.h`), `web/web_page.h` the
single HTML/JS page (raw string literal in PROGMEM). Keep image work in the browser; the
ESP32 only handles 418-character hex bitmaps (`logic/bitmap_format.h`, MSB = left dot).
- The Random effect's list (`Settings::random_effects`) is only known to the ESP32:
`FlipdotFrames::_useEffect()` picks an effect per frame and sends that, so the Nano doesn't
run its own `EFFECT_RANDOM` (which picks from all effects).
- Settings: `logic/settings.h` struct with defaults = original behaviour, stored as an NVS
blob with a version (`system/settings_store.cpp`). When the struct changes, bump
`VERSION` there (old records then fall back to defaults). Only the current version is