Output Panel

Studio captures every std.log message — the engine, the editor, and (in Play mode) your own scripts — into the Output panel, colored and timestamped the same way it prints to the terminal.

Where it lives

Output is a regular dockable panel, tabbed alongside Assets by default. Drag it, tab it with something else, or float it like any other panel; toggle it from View ▸ Show Output.

Logging from your own code

See Components: Logging for how to log from a script. In short: use plain std.log (optionally std.log.scoped(.my_script) for your own category) — it shows up here in Play mode, and in a built game's console.

Filtering

  • Level icons (bug / info / warning / error) toggle each severity — highlighted when shown.
  • Category dropdown narrows the list to one scope (your own script's, or an engine subsystem's) — "All" shows everything.
  • Search box matches message text (case-insensitive).
  • "..." ▸ Show system messages (off by default) reveals SDL/dvui's own internal chatter, bucketed under a single Studio category — off by default so your own and your game's messages lead.

All of these combine, and also apply to Copy.

Collapsing repeated messages

  • Consecutive identical messages always collapse into one row with an ×N badge, regardless of the toggle below.
  • Collapse (toolbar toggle) additionally merges every matching message anywhere in the visible history into one row with a running total — Unity's "Collapse" button, for when the same warning fires on and off throughout a session.

Opening a source location

When a message contains a recognizable file:line reference, it's shown inline. Double-click the row to open it in your configured editor — set $VISUAL or $EDITOR (recognizes code, code-insiders, subl, zed, vim/nvim); otherwise it falls back to your OS's default handler for the file (no line jump).

Stack traces

Error entries that captured a stack trace show a ▸/▾ arrow — click it to symbolize and reveal the trace (done lazily, only when expanded, since symbolizing has a real cost). Entries with no trace (most non-error messages) show no arrow at all.

Auto-scroll, Clear, Copy

  • Auto-scroll (on by default) keeps the view pinned to the newest message, console-style; uncheck it to read back through history without fighting new output.
  • Clear empties the log.
  • Copy copies every currently-visible entry (respecting your filters and Collapse) to the clipboard, oldest first — handy for pasting into a bug report or an AI assistant.

← All docs Edit this page