Panels, Status Bar and Notifications
This page explains how to arrange panels in the editor and how the editor tells you about work that runs while you keep working: the status bar, the running-work indicator and notifications.
Docking panels
Every panel can be dragged by its tab and docked at any edge of another area, added as a tab, or torn off into a floating window. While you drag, the drop target shows where the panel will go, for example Dock at the left edge of the window.
There are two kinds of panels:
- Main window panels, such as the Asset Browser, Log or Background Operations, exist once for the whole editor.
- Document panels, such as the Properties or scene tree panel of a scene, belong to a document. Every open document has its own.
Document panels in the main window
Document panels can live inside their document's tab, or anywhere in the main window, next to the main window panels or in a floating window. To move one out, drag its tab out of the document, or right-click the tab and choose Move to the main window. To put it back, right-click it and choose Back into the document.
A document panel in the main window follows the active document. If you dock a scene's Properties panel next to the Asset Browser, that place shows the Properties of whichever scene is active. When you switch to a scene, its panel takes the place. When you switch to a document of another type, for example a material, the place has nothing to show and folds away, and its neighbours take the space. A floating window that only holds such panels hides. Both come back where they were once a document of that type is active again.
Some more details:
- Documents of the same type share one layout. Moving a scene's panel moves it for every scene.
- When two documents of the same type show side by side, the active one has an accent line on top of its tab.
- When all of a document's panels are in the main window, the document says All of this document's panels are in the main window.
- Closing a floating window, or a document panel in a floating window, puts the panel back into its document, closed.
The editor saves the layout of the main window and of each document type within a few seconds of a change. Windows reopen only on monitors that are still connected, so a floating window is never restored off-screen.
Status bar
The status bar at the bottom of the main window and of each document shows short messages, for example Document saved or Copied path: .... Some messages stay as long as they apply:
- READ-ONLY: and the reason, while the project is open read-only.
- Restart the editor to apply changes. or Reload the project to apply changes. after you changed a setting that needs it.
- The saved state of the document, for example Unsaved: saved state 3 steps back. See Undo history.
Running work
Long operations, such as transforming a batch of assets, building C++ code or exporting a project, show as a pill in the status bar once they have run for half a second. The oldest operation is shown first. Work that belongs to another document is named with that document's file. When no document's status bar is visible, the indicator shows as a chip in the title bar instead.
Click the pill to list everything that is running. Each entry has Cancel and Show. When nothing is running, the list says Nothing is running and offers Open Long Ops Panel, which opens the Background Operations panel.
Notifications
When work that you did not wait for has finished, a notification (toast) appears in the bottom-right corner of the main window, above the status bar:
- Failures always get a notification, with the reason and a Show in Log button where the log has details.
- Successes get one when the work ran in the background, or when it showed a progress window for at least two seconds.
- Cancelled work only gets one when it was not you who cancelled it, for example when the engine process stopped.
- Background asset transforms are reported per batch, for example Transformed 42 assets or Transformed 42 assets, 2 failed. A batch that succeeds is only reported from 10 assets on, so saving a single asset does not raise a notification every time.
Waiting for the engine process
Some editor operations have to wait for a reply from the engine process. Most replies take milliseconds, so the editor waits silently at first. If the wait takes longer, the status bar shows Waiting for the engine process (...) with the seconds that passed, while the editor keeps drawing. Input you make in the meantime is queued and runs once the wait is over. Only after five seconds does the Waiting for Engine Process dialog open. Waits are bounded: if the engine process is gone or the wait looks stuck, the operation fails instead of hanging the editor.