diff options
| author | Luke Hoersten <[email protected]> | 2026-06-21 11:34:59 -0500 |
|---|---|---|
| committer | Luke Hoersten <[email protected]> | 2026-06-21 11:34:59 -0500 |
| commit | ba412e5a17e63dffe18f69a6af2e2e27ef470778 (patch) | |
| tree | 72b753bf40d30cbd522fb1da3bc62a1db43aa2d3 /main/jpeg_decoder.c | |
| parent | 2dc9dd176f5577158430e0f4f6a20b7dee8c5646 (diff) | |
scrypted: drop OnOff — empirically StartStop is what the Scripts UI binds to
In v101fb3e we shipped StartStop + OnOff side-by-side to see which
the 'Status and Controls' panel actually wired to. The v44c7a63
diagnostic session confirmed: clicking STOP fires stop() (StartStop),
not turnOff() (OnOff). User's console showed:
lifecycle: start() called (running=false)
...
lifecycle: stop() called (running=true)
stop: tearing down 1 resources
So StartStop alone is the right interface. OnOff just produced a
duplicate 'Status and Controls' panel for the same lifecycle. Drop it.
Also dropping the verbose lifecycle: ... logging — we know the
binding now. The cleanup mechanism is the load-bearing observable
('stop: tearing down N resources' from drainShutdownCleaners).
The status text still rendering 'Unknown' (rather than Running/Stopped)
is a separate cosmetic concern — possibly the duplicate panels were
confusing the UI; with a single StartStop panel left, the displayed
status may now reflect this.running correctly. To be verified.
Diffstat (limited to 'main/jpeg_decoder.c')
0 files changed, 0 insertions, 0 deletions