Finding Problems

Start with the Problems panel. Each message should name the affected file and location. Click a message to open that place in the editor.

Read a Problems entry

Each row shows a colored severity dot, its numbered code, a source tag, the message, and the location. Click the code to open its meaning on the Diagnostic codes page; click anywhere else on the row to jump to that file and position in the editor.

The source tag is daemon or editor:

• daemon comes from a connected calmui dev session revalidating your project's compiled CSS the same way the compiler and layout engine will. Its position is the exact file, line, and column you authored, including a scoped <style> block inside a .calmui file or a rule in a global .css file.
• editor comes from Studio's own language service checking the file as you type, before a daemon confirms it.

When both would report the same source position, only the daemon's numbered entry is kept; the editor's is a preliminary check that the daemon's pass supersedes once it runs.

If the preview does not update

1. Save the open file.
2. Fix errors shown in Problems.
3. Check the status near the preview.
4. Click Restart Preview if the preview pane failed.
5. If you are checking Unreal, confirm that Unreal → Connection shows Connected.

CalmUI keeps the last working preview when a new save contains an error.

Inspect an element

Click an element in Preview or select it in Hierarchy. The Inspector shows its source, size, spacing, bindings, and focus state. Use Unreal → Action Log for received action information.

Switch the preview to Unreal when you need information from the screen running in Unreal Editor.