RmlUi implementation boundary
Section titled “RmlUi implementation boundary”Inno.Native.UI implements the native bridge used by the managed RmlUi adapter. Ordinary engine consumers use UI documents and neutral render frames rather than direct native calls.
ABI and ownership contract
Section titled “ABI and ownership contract”The managed backend owns sessions, documents, event transfers and frame acknowledgment. Shared process resources retain their owner-thread and final-session lifetime requirements. A frame is acknowledged only after the required transfer completes; borrowed input and native output storage cannot outlive their owners.
Session/document handles are transient implementation identities. They do not replace persistent IDs or managed resource ownership. The product must deploy a matching native module; a missing dependency remains an error.
Read UI lifetimes, render-frame consumption and RmlUi integration for the engine-facing contracts.
Documentation scope
Section titled “Documentation scope”Raw C exports, generated storage layouts and binding members are outside this documentation. The UI toolchain still explains preparation ownership, and native integration tests still validate the actual implementation.