> 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/2024.1/objects-and-types/scene2d-objects/gui/slider.md).

# Slider

The **Slider** is a **GUI** **2D Object** that allows the user to create a customizable slider selector. The customization is done through the [**Attributes**](#attributes).

![Slider.](/files/93oJa9aLr6bFR2DK4az4)

## Attributes

The **Object's** **Attributes** can be used to fully customize the **Object**. Explained below, they are:

* [**Transformation**](#transformation)
* [**Slider**](#slider)
* [**Style**](#style)
* [**Tag**](#tag)

### Transformation

![Transformation Attributes.](/files/GYGZGpN1FDsiT38ptmlw)

The `Transformation` **Attributes** deal with placement, rotation, and size in *XY* space. More information can be found [here](/incari-studio/2024.1/objects-and-types/attributes/common-attributes/transformation.md).

### Slider

The **Slider Attributes** offer the user options to customize the **Slider**:

![Slider Attributes.](/files/XEGJusT01BQYXiM3X7q0)

* `Value` determines where the handle will appear on the track on start.
* `Minimum` is the leftmost value that occurs on the track.
* `Maximum` is the rightmost value that occurs on the track.
* `Step` is the amount the values increase to the next.

### Style

The **Style Attributes** offer the user options to customize further visual aspects of the **Slider**:

![Style Attributes.](/files/gNklnM4zDlilbXVLI7rj)

* `Handle color` is the color of the handle (the sliding object along the track)
* `Handle size (px)` is the size of the handle.
* `Track Color` is the color of the track (the line that appears as part of the **Slider**).
* `Track thickness (px)` is how thick the track appears.
* `CSS Classes` contain the *CSS* class names of the **Object**.
* `Stylesheet` contains the *CSS* stylesheet of the **Object**. This can override any stylesheet provided in the [**Project Settings**](/incari-studio/2024.1/modules/project-settings/style.md) or a [**Scene2D**](/incari-studio/2024.1/objects-and-types/project-objects/scene2d.md). To address these in the **Logic**, please refer to the [**Object 2D Nodes**](/incari-studio/2024.1/toolbox/incari/object2d.md).

Finally, the **Slider** works like this when the **Project** is run:

![Slider example.](/files/2ynaMgW9H47N5RpO7p8b)

### Tag

![Tag Attributes.](/files/AcVS9u9EJzK2klOH2pFq)

This **Attribute** manages the *tags* for the **Slider**. See more on *tags* [here.](/incari-studio/2024.1/objects-and-types/attributes/common-attributes/tag.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/2024.1/objects-and-types/scene2d-objects/gui/slider.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.