> For the complete documentation index, see [llms.txt](https://docs.incari.com/incari-studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.incari.com/incari-studio/2023.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardpressed.md).

# On On-Screen Keyboard Key Pressed

## Overview

![The On On-Screen Keyboard Key Pressed Node.](/files/e5Rj1RIUkEpov46mV88B)

The **On On-Screen Keyboard Key Pressed Node** is an **Event Listener** **Node** used for executing a **Logic Branch** when any key on the **On-Screen Keyboard** is pressed.

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

## Attributes

![The On On-Screen Keyboard Key Pressed Node Attributes.](/files/sLz9MZU8vXElYei0qzsS)

| Attribute | Type         | Description                                                                                                                                      |
| --------- | ------------ | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| `Object`  | **ObjectID** | The **On-Screen Keyboard** in which the pressing of any key 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 the pressing of any key 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.                                                                                 |
| `Symbol Entered`   | **String**   | The symbol that was clicked on 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/2023.1/toolbox/incari/event/unsubscribe.md) to unsubscribe from the **Event**. |

## See Also

* [**On On-Screen Keyboard Enter Pressed**](/incari-studio/2023.1/toolbox/events/on-screenkeyboard/on-onscreen-keyboard-enter-pressed.md)
* [**On On-Screen Keyboard Input Changed**](/incari-studio/2023.1/toolbox/events/on-screenkeyboard/on-onscreen-keyboard-input-changed.md)
* [**On On-Screen Keyboard Arrow Down Pressed**](/incari-studio/2023.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardarrowdownpressed.md)
* [**On On-Screen Keyboard Arrow Up Pressed**](/incari-studio/2023.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardarrowuppressed.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.incari.com/incari-studio/2023.1/toolbox/events/on-screenkeyboard/ononscreenkeyboardpressed.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.