Build-to-UI error reference
Use the symptom to narrow the cause before editing.
| Symptom | Check and action |
|---|---|
| KuiConfig.cmake not found | Point Kui_DIR to SDK/cmake rather than include or bin and check extraction. |
| LNK2019 / unresolved external | Match the imported target to the SDK layer, then check architecture, configuration and components. |
| Missing DLL / startup failure | Inspect destination files against helper output and launch with the matching runtime group. |
| HTML edits do not appear | Rebuild generated headers in embedded projects and verify the launched executable, closing the old instance. |
| Save reads old input | Read current value() instead of the initial value attribute. |
| DevTools cannot connect | Enable debugging, maintain polling, rediscover the port and target, and check stale authentication. |
Page and layout problems
For a blank page, check document loading, resource paths and node existence. For sizing, inspect actual boxes and computed styles before selectors, fixed widths and scroll containers. Change a small set of rules at a time.
Script and event problems
If a control exists but does nothing, check handler setup, element type and callback errors. For Lua, also check engine creation, document binding, script execution and lifetime. Inspect current values at a breakpoint rather than relying on initial HTML attributes.
Send a minimal reproduction
Include OS and architecture, core/binding versions, build configuration, exact command and error text. UI issues also need minimal HTML/CSS, viewport, scale, steps and expected versus actual behavior. Remove private data, authenticated URLs and tokens.
Something unclear?
Report an issue on this page →