> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/flatredball/api/flatredball-forms/controls/button.md).
# Button
### Introduction
Button is a standard clickable object with states for enabled (default), hover, pressed, and disabled.
### Layout Requirements
The Button control has no requirements - an empty container is sufficient.
### TextInstance
The Button control can optionally include a Text instance named **TextInstance**. Setting the Button control's **Text** property changes the **TextInstance's** displayed string.
### Code Example
Buttons provide events for Click and Push events. The following code shows how to handle these events on a button obtained from a gum runtime object named **ButtonInstance**:
```lang:c#
void CustomInitialize()
{
var button = TutorialScreenGum
.GetGraphicalUiElementByName("ButtonInstance")
.FormsControlAsObject as Button;
button.Click += HandleButtonClick;
button.Push += HandleButtonPush;
}
private void HandleButtonClick(object sender, EventArgs e)
{
// handle click logic here
}
private void HandleButtonPush(object sender, EventArgs e)
{
// handle push logic here
}
```
### Code Example - Code-Only Creation
```lang:c#
void CustomInitialize()
{
// This will construct a button using the default
// visual which should be set-up by Glue, or which can be
// manually set up in code.
var button = new Button();
button.Visual.AddToManagers();
button.Text = "Hello";
button.Click += HandleButtonClick;
button.Push += HandleButtonPush;
}
private void HandleButtonClick(object sender, EventArgs e)
{
// handle click logic here
}
private void HandleButtonPush(object sender, EventArgs e)
{
// handle push logic here
}
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.flatredball.com/flatredball/api/flatredball-forms/controls/button.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
