# On On-Screen Keyboard Input Changed

## Overview

![The On On-Screen Keyboard Input Changed Node.](/files/Vq2s5MYi313b3CsrDbal)

The **On On-Screen Keyboard Enter Pressed** **Node** is an **Event Listener** **Node** used for executing a **Logic Branch** when the input of an **On-Screen Keyboard** is changed.

[**Scope**](/incari-studio/2024.1/toolbox/overview.md#scopes): **Scene**, **Prefab**.

## Attributes

![The On On-Screen Keyboard Input Changed Node Attributes.](/files/ZPuFYcuLPsa7qPM28jlu)

| Attribute | Type         | Description                                                                                                                              |
| --------- | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `Object`  | **ObjectID** | The **On-Screen Keyboard** in which an input change triggers the **Logic Branch**, if none is given in the `Object ID` **Input Socket**. |

### Inputs

| Input           | Type         | Description                                                                        |
| --------------- | ------------ | ---------------------------------------------------------------------------------- |
| `Object ID`     | **ObjectID** | The **On-Screen Keyboard** in which an input change triggers the **Logic Branch**  |
| `Subscribe` (►) | **Pulse**    | An **Input Pulse** that needs to be triggered to start listening to the **Event**. |

## Outputs

| Output             | Type         | Description                                                                                                                                                                                                            |
| ------------------ | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse**    | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution.                                                                                 |
| `Keyboard Input`   | **String**   | The input of the **On-Screen Keyboard**.                                                                                                                                                                               |
| `Object ID`        | **ObjectID** | The **On-Screen Keyboard** received as **Input**.                                                                                                                                                                      |
| `Event ID`         | **ObjectID** | The ID of the current **Event**. This can be connected to the [**Unsubscribe Node**](https://github.com/cgi-studio-gmbh/incari-doc/blob/2024.1/toolbox/incari/event/unsubscribe.md) to unsubscribe from the **Event**. |

## See Also

* [**On On-Screen Keyboard Enter Pressed**](/incari-studio/2024.1/toolbox/events/on-screenkeyboard/on-onscreen-keyboard-enter-pressed.md)
* [**On On-Screen Keyboard Arrow Down Pressed**](/incari-studio/2024.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardarrowdownpressed.md)
* [**On On-Screen Keyboard Arrow Up Pressed**](/incari-studio/2024.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardarrowuppressed.md)
* [**On On-Screen Keyboard Key Pressed**](/incari-studio/2024.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardpressed.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/2024.1/toolbox/events/on-screenkeyboard/on-onscreen-keyboard-input-changed.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.