Focus
Controls how a node may take the focus ring: never, only by a pointer press, or normally. Names a neighbour for a direction or the Tab order when the computed answer is wrong. Goes under a Canvas.
On this page
Add it
+ Add node → Text Entry creates a node with it already on. Already have a node for it? Add component → FocusComponent.
From a script
A script on the same node writes these fields by name. FocusComponent is the name to pass.
rgs
set_text("FocusComponent", "up", "");
set_text("FocusComponent", "down", "");
set_text("FocusComponent", "left", "");
set_text("FocusComponent", "right", "");
set_text("FocusComponent", "next", "");
set_text("FocusComponent", "previous", "");Fields
| Field | Script name | Kind | Default | What it does |
|---|---|---|---|---|
| Mode | mode | one of None, Click, All | All | How this node may be focused. |
| Subtree Focus | subtree_focus | one of Inherit, Deny, Allow | Inherit | Whether the ring may enter this subtree. |
| Subtree Pointer | subtree_pointer | one of Inherit, Deny, Allow | Inherit | Whether pointers may enter this subtree. |
| Up | up | text | empty | Node to focus on up; empty computes it. |
| Down | down | text | empty | Node to focus on down; empty computes it. |
| Left | left | text | empty | Node to focus on left; empty computes it. |
| Right | right | text | empty | Node to focus on right; empty computes it. |
| Next | next | text | empty | Next in the Tab order; empty uses reading order. |
| Previous | previous | text | empty | Previous in the Tab order; empty uses reading order. |
Buttons
- Clear Links Forget every pinned neighbour and compute navigation from the rects again