3 Commits

Include renames

Author	SHA1	Message	Date
tfaour	fcf3aec4c0	Move button actions to per-widget config, add hold-for-global-action ... Next/back button assignment moves from a frame-level "Button assignments" card into each widget's own gear-icon dialog, prefilled with a sane default at creation (photos/calendar -> advance/back, whiteboard/weather -> check_now, others -> none). At most one binding per (widget, button) now -- cross-widget execution order never mattered since each widget's action only touches its own state. New firmware capability: holding NEXT or BACK past a configurable duration (min 3s, server-side default) triggers a frame-wide action instead of the per-widget short-press one -- cycling saved layouts, refreshing all widgets, or freezing/unfreezing every photo widget (see app/global_actions.py). Firmware next/back checks gain the same hold-duration polling the combo button already had; the threshold comes from the previous wake's /frame/config fetch (persisted in NVS), since this wake's button decision happens before that request. Not done here: firmware/version.txt is intentionally left unbumped -- this hasn't been built or hardware-tested (no ESP-IDF toolchain in this environment), so no firmware release build should be triggered yet.	2026-07-27 22:09:33 +00:00
tfaour	289d308b57	Disambiguate same-type widgets in the button-assignment dropdowns ... Two widgets of the same type (e.g. two Photos widgets) both showed up as plain "Photos" with no way to tell which was which. The buttons API now includes each widget's grid placement plus the frame's grid dims; the UI derives a rough position ("top-left", "right", etc.) from that and only appends a number+position suffix when a type actually repeats on the frame, leaving the common single-widget-per-type case unchanged.	2026-07-24 18:00:01 -04:00
tfaour	8b9f636cce	Mark whiteboard as (alpha); add the Phase 5 button-assignment UI ... Whiteboard rendering isn't fully reliable yet -- tag it (alpha) everywhere it's user-facing (widget label, add-widget button, dialog title, Settings' WebDAV section) via one shared WIDGET_LABELS map (moved to common.js so both the Layout canvas and the new Configuration tab section can use it). Button assignments: a new "Button assignments" card on the Configuration tab lets you assign an ordered list of (widget, action) bindings to each physical NEXT/BACK button -- add/remove/reorder, all autosaved. Backed by new GET/PUT /api/frames/{id}/buttons endpoints; PUT replaces a button's whole list in one atomic, fully-validated call rather than separate add/remove/reorder endpoints. Device-side consumption already existed (routers/device.py's _run_button_actions); this is the UI for what was previously only reachable via the default migration mapping.	2026-07-24 17:13:51 -04:00