# Layouts

### Docking

User interface is designed with docking functionality in mind. Once you add a new scope and start dragging it, you will see highlighted areas where it can be placed and docked:

![Docking regions](/files/-MHobEBV4oPybgBP96cM)

Docking feature helps you fill the whole real estate nicely and scale properly when resizing application window / changing resolution / etc.

Quick docking demo:

![](/files/-MHobmILiRJ7Xyarv1RR)

### Layout Switching

Quickly define and toggle between your workspaces using layouts. Each scope configuration can be saved and reloaded from the Layout menu, keyboard shortcut and even with a **StreamDeck** action which makes it super easy to switch from one to another.

### Even Scope Sizing

Available from **1.11.45**.

The **Layout** menu includes two commands for normalizing docked scope sizes:

* **Size all scopes to even width** - makes scope columns the same width.
* **Size all scopes to even height** - makes scope rows the same height.

For example, if the scope area is 3840 pixels wide and four scopes are docked side by side, **Size all scopes to even width** gives each scope column an equal share of the width. If the scope area is 2160 pixels high, **Size all scopes to even height** gives two rows equal 1080-pixel shares, or three rows equal 720-pixel shares.

The commands resize the dock layout itself. Splitter gutters, tabs, title bars and fixed aspect-ratio scope settings can reduce the exact visible render area by a few pixels.

### Multi-monitor layouts (1.11.8+)

When using a Secondary Window, layouts store the positions and sizes of scopes across both windows. Loading a layout restores both windows; if only one monitor is available, scopes are arranged on the active display.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.timeinpixels.com/nobe-omniscope/layouts.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.