Connect FLTK shell to JACK engine controls and status
This commit is contained in:
parent
577d80f018
commit
2ecc03b482
14 changed files with 691 additions and 45 deletions
|
|
@ -26,12 +26,18 @@ format/xrun/loss status, start/stop/reopen, and bounded pending/retired plan
|
|||
handoff using lock-free atomics. Hardware-independent failure/concurrency tests
|
||||
and a 30-second software-loopback run pass. See decision 0004 and AUDIO_ENGINE.md.
|
||||
Physical hardware playback/endurance and live server-loss recovery remain
|
||||
unverified; no GUI engine integration until Phase 3.
|
||||
unverified; GUI engine controls are implemented in Phase 3.
|
||||
|
||||
## Phase 3 — FLTK shell
|
||||
Main window, transport controls, view switching, backend status, clean startup
|
||||
and shutdown through the C API.
|
||||
|
||||
Implemented: dark FLTK shell, Play/Stop/Reconnect, view/menu shortcuts, backend
|
||||
state/format/xrun/process status, persistent command errors, timer-based refresh
|
||||
and retirement collection, and callback-safe close/retry. Mock-backend GUI tests
|
||||
and live GUI/JACK start/stop/reconnect/close tests pass under Xvfb. Editors and
|
||||
project-file actions remain placeholders; engine runs in silence. See GUI.md.
|
||||
|
||||
## Phase 4 — Modular editor
|
||||
Draw nodes/ports/edges; create, move and connect nodes; reject invalid edges;
|
||||
safely submit edits to the C core.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue