# Touchable Area

The **Touchable Area** handles the basic touch interactions, such as tap, slow tap, multi-tap, hold, press, and release, but only for touches within its defined boundaries. Each type of **Touchable Area** provides different methods for defining its interaction region, which could be a box, circle, or other shapes.

<figure><img src="https://348920791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeQ7CIxHuad77enwt80mG%2Fuploads%2FDCHHVGYe7pyqvN9MouW9%2Fimage.png?alt=media&#x26;token=25e3a0c0-4917-497f-ac6b-941dbb84b15a" alt=""><figcaption></figcaption></figure>

## Parameters

All Touchable Area types inherit the following base parameters. Depending on the specific type, additional parameters may also be available.

* **`Raycast`** : Determines if a raycast will perform at the touched point to detect if another graphic element obstructs the interaction. Use a Layer Mask to filter objects affected by the raycast.
* **`Auto Press`** : If enabled, automatically perform press to a finger that enters the defined area. You can also choose whether fingers already used by another Tactile Control are allowed to trigger this behavior.
* **`Auto Release`** : If enabled, automatically perform release to a finger that leaves the defined area.
* **`Multi Touch`** : Allows multiple fingers to interact with the control at the same time.

### Interaction Config

Each Tactile Control can have its interaction configuration overridden. By default, timing values are sourced from the Input Settings Asset located at ***Project Settings > Input System Package > Settings***.

* **`Tap Time`** : The time (in seconds) within which a press and release has to occur for it to be registered as a tap. When toggled, uses a specified custom tap time; otherwise, uses the default.
* **`Slow Tap Time`** : The minimum duration required of a press-and-release interaction to evaluate to a slow-tap-interaction. When toggled, uses a specified custom slow tap time; otherwise, uses the default.
* **`Multi Tap Delay Time`** : The maximum duration that may pass between taps in order to evaluate to a multi-tap-interactionWhen toggled, uses a specified custom multi tap delay time; otherwise, uses the default.
* **`Hold Time`** : The minimum duration required of a press-and-release interaction to evaluate to a hold-interaction. When toggled, uses a specified custom hold time; otherwise, uses the default.
* `Tap Radius` :  The maximum radius that a touch contact may be moved from its origin to evaluate to a tap-interaction. When toggled, uses a specified custom hold time; otherwise, uses the default.
* `Hold Radius` : The maximum radius that a touch contact may be moved from its origin to evaluate to a hold-interaction.

## Debug Gizmos

Expanding the Touchable Area drawer section activates its **Scene View Gizmos**, which visually displays the defined interaction area using dotted border lines.

<div align="center"><figure><img src="https://348920791-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FeQ7CIxHuad77enwt80mG%2Fuploads%2FqcYSllXOI7EWENG4vkW3%2FTactile_TouchableArea_Gizmo.gif?alt=media&#x26;token=6f47935f-6ee0-4fe1-b8ec-eea401aa3002" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
The default Gizmos color is **White**. However, the color changes to indicate specific states:

&#x20;  • <mark style="color:yellow;">**Yellow**</mark>: The Tactile Control is not interactable. \
&#x20;  • <mark style="color:red;">**Red**</mark>: No Touchscreen device is detected.&#x20;

These visual cues help quickly identify issues during development.
{% endhint %}


---

# 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://niam.gitbook.io/documentation/game-creator-2/tactile/touchable-area.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.