One completed C_elm_mwnd_msg entry retained by MULTI_MSG/NEXT_MSG.
The active page remains in MwndState so existing form handlers can mutate it
without an additional indirection; completed pages are immutable snapshots.
Which object event an OBJECT property op drives, looked up by op code.
These ran as chains of about fifty comparisons on every object property
read and write (a tenth of the VM’s frame time in particle scripts).
Cross-platform replacement for the native Syscom dialogs used by the
original Windows build when a project does not provide SAVE_SCENE,
LOAD_SCENE, CONFIG_SCENE, or CANCEL_SCENE. The dialog itself is rendered
by the engine and receives input through the normal winit path, so the same
state machine is used on desktop, mobile, and WebAssembly hosts.
The runtime’s tables (objects, stage lists, properties) are keyed by
small integers and looked up many times per object operation; SipHash
was about a tenth of the VM’s frame time on consoles.