# Text

This function block lets you place editable text directly on the scene canvas. It is a lightweight visual/textual annotation tool meant for labels, notes, or instructions inside your scenario layout.

## 📥 Inputs <a href="#inputs" id="inputs"></a>

This function block does not have any input sockets.

## 📤 Outputs <a href="#outputs" id="outputs"></a>

This function block does not have any output sockets.

## 🕹️ Controls <a href="#controls" id="controls"></a>

`Text` Editable multi-line text area where you can type and format the text that appears on the scene canvas.

## 🎨 Features <a href="#features" id="features"></a>

* Simple, resizable on-canvas text area for adding descriptions, reminders or scene annotations.
* Keeps text visible while designing scenarios so you and collaborators can document intent or usage directly in the workspace.
* Text stays in the scene and is preserved when the scene is saved.

## 📝 Usage Instructions <a href="#usage" id="usage"></a>

1. Drag the block onto your scene canvas.
2. Click inside the `Text` area and type your message.
3. Move or resize the block on the canvas to place the text where it best explains the layout or flow.

## 📊 Evaluation / Runtime Behavior <a href="#evaluation" id="evaluation"></a>

This block is for visualization and documentation inside the editor. It does not participate in data flow or processing — it does not accept inputs or produce outputs during scenario runs.

## 💡 Tips and Tricks <a href="#tips-and-tricks" id="tips-and-tricks"></a>

* Use this block to leave short instructions for operators or notes about expected inputs and outputs near relevant blocks such as `Show Image` or `Write Text On Image`.
* Combine with `Write Text On Image` when you want the same text to appear both on the canvas (for documentation) and overlayed on actual images during processing or export.
* Use alongside `Image Logger` or `Image Write` to reference naming conventions or logging notes directly on the scene, helping you keep track of saved files.
* For interactive input that feeds text into processing pipelines, pair with `String Input` so you can both display and use the same text in automated steps.

## 🛠️ Troubleshooting <a href="#troubleshooting" id="troubleshooting"></a>

* If your text is hard to read on the canvas, move the block to a clear area or resize it for better visibility.
* If you expect text to affect processing, remember this block does not output data; use `String Input` or `Write Text On Image` for text that needs to be consumed by other blocks.


---

# 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.augelab.com/function-blocks/blocks-reference/input-output/data-inputs/text.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.
