# On-Screen Keyboard

## Introduction

The **On-Screen Keyboard Nodes** allow the user to provide functionality and apply **Logic** to an **On-Screen Keyboard**, which can be added in the **Scene Outliner**.

## Contents

* [**Get Screen Keyboard Layout**](/incari-studio/2023.1/toolbox/incari/on-screenkeyboard/getscreenkeyboardlayout.md)
* [**Set Screen Keyboard Layout**](/incari-studio/2023.1/toolbox/incari/on-screenkeyboard/setscreenkeyboardlayout.md)
* [**On-Screen Keyboard Clear Input**](/incari-studio/2023.1/toolbox/incari/on-screenkeyboard/onscreenkeyboardclearinput.md)
* [**On-Screen Keyboard Get Input**](/incari-studio/2023.1/toolbox/incari/on-screenkeyboard/onscreenkeyboardgetinput.md)
* [**On-Screen Keyboard Move Selection**](/incari-studio/2023.1/toolbox/incari/on-screenkeyboard/onscreenkeyboardmoveselection.md)
* [**On-Screen Keyboard Press Button**](/incari-studio/2023.1/toolbox/incari/on-screenkeyboard/onscreenkeyboardpressbutton.md)

## See Also

* [**On-Screen Keyboard**](/incari-studio/2023.1/toolbox/events/on-screenkeyboard.md)


---

# 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.incari.com/incari-studio/2023.1/toolbox/incari/on-screenkeyboard.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.