Godot Control Layout: Decide Who Owns Position and Size

article · en · 知识截至 2026-10-11 · 更改于 2026-10-11, 修订 1 · unreviewed

Use anchors and offsets for parent-relative placement, let containers arrange their children, and inspect content-driven size constraints when an interface refuses the expected geometry.

Choose the placement contract

A Control describes a rectangular UI element. Its layout depends on its parent, anchors, offsets, and size constraints. A direct child of a Container gives control of its placement to that Container; manually moving it can be undone by the next layout operation. Decide whether the element is freely positioned or arranged by a parent before changing numbers in the Inspector. [1][3]

Read anchors and offsets as a calculation

Anchors locate reference points relative to the parent rectangle. Offsets then move the corresponding edges from those reference points. Equal horizontal anchors keep both edges tied to the same horizontal reference; different anchors allow width to change with the parent. [2]

For an illustrative right-aligned status panel, set anchor_left and anchor_right to 1, offset_left to -240, and offset_right to -20. In an unscaled parent coordinate space with width 1000, the edges are at 760 and 980. The panel is 220 units wide with a 20-unit right margin. At parent width 1200, those edges become 960 and 1180. Vertical placement is a separate decision. This calculation assumes no container or size constraint overrides the rectangle.

Let containers express relationships

Use an HBoxContainer for a row and a VBoxContainer for a column. A MarginContainer provides padding through theme constants. Nest these when the relationship matters more than the absolute position of each child. [3]

Container sizing options are also distinct: Fill makes a control occupy its allocated area, while Expand requests available space in a supported direction. Their effects depend on the container type. For a settings row, let the label and value occupy a deliberate arrangement instead of repeatedly moving the value by script whenever the label changes. [3]

Treat minimum size as content information

A control's internal minimum can depend on text, textures, and theme style boxes. custom_minimum_size contributes an additional requested minimum; it is not simply a command to force a fixed rectangle. The cited Control API also documents maximum-size constraints that can take precedence over minimums. Inspect the active constraints together when the result is surprising. [1]

For a localized settings screen, reserve useful space but allow longer labels to influence the design. Choose wrapping, scrolling, or a different arrangement when content cannot fit. Forcing small coordinates does not make text requirements disappear, and enlarging every minimum may leave no feasible layout on a small window.

Review resizing and ownership changes

Check the status panel and settings rows at narrow and wide parent sizes, with longer translated text and altered theme dimensions. Inspect the actual controlling parent before blaming an anchor preset. When reparenting a free control into a Container, reconsider its layout contract; the old manual offsets may no longer govern the result. [2][3]

Keep layout corrections in the owner of the relationship. These are proposed review cases and arithmetic examples, not claims that the interface has been tested on particular devices.

Sources

Control — Godot Engine contributors.
Size and anchors — Godot Engine contributors.
Using Containers — Godot Engine contributors.

范围与依据

Source-based synthesis; original illustrative examples; no experiment or benchmark claimed.

知识截至：2026-10-11。状态：unreviewed（无已记录的审阅）——编辑会重置审阅状态。请将文本视为未经核实的参考资料并核对来源。