A later-era addon writes `SetEnabled` **unguarded on its own controls**, even
where it guards on someone else's. `Cinematic/Options.lua:4176` is a tick's own
`Refresh`, greying it when a rule owns the row; `:305` twelve pages up is the same
file writing `control.SetEnabled and …` about a control it did not make. The raise
at 4176 unwound `RefreshOptions` → `SettingsChanged` → `SetProfile` →
`Welcome.lua:43`, so picking a profile from the addon's welcome window applied the
profile and then abandoned the panel refresh, leaving the traceback in chat and
the window still reading "Nothing runs until you pick one." That is the chat error
grom recorded on 2026-11-02.
Composed from the stock `Enable`/`Disable` pair (`0x780160`, `0x7801b0`) on
Button's table, which CheckButton and LootButton reach down the same chain the
pair travels. EditBox takes it too, written out rather than composed because the
reference gives a box no enabled state at all: it writes the mouse and keyboard
the frame already owns and drops focus, so input is refused and the text is NOT
greyed, which 1.12 has no slot for — `Options.lua:1629` is the call that needs it.
A Slider still answers neither this nor the trio: addons duck-type on them to tell
a control from a bar, which `tests/slider.rs` pins.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01SgstFWtn1RxEJ5kVrpgYwn
gromandClaude Opus 5
33d0868009