> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/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/gum/code/standard-visuals/coloredrectangleruntime.md).

# ColoredRectangleRuntime

{% hint style="info" %}
ColoredRectangleRuntime is the legacy solid-color rectangle. New Gum projects (version 3 and later) seed the **Rectangle** standard instead, which is backed by [RectangleRuntime](/gum/code/standard-visuals/rectangleruntime.md). RectangleRuntime renders fill, outline (stroke), gradients, and drop shadows, so prefer it for new code. ColoredRectangleRuntime remains fully supported for existing projects.
{% endhint %}

### Introduction

The ColoredRectangleRuntime is a visual object which displays a solid-color rectangle. It can be used to display solid colors, but can also display gradients.

ColoredRectangleRuntime is often used as a colored background or a health bar.

### Code Example

The following code creates a ColoredRectangleRuntime:

```csharp
var coloredRectangleRuntime = new ColoredRectangleRuntime();
coloredRectangleRuntime.Color = Color.White;
coloredRectangleRuntime.Width = 100;
coloredRectangleRuntime.Height = 100;
coloredRectangleRuntime.AddToManagers();
```

The output is a white rectangle:


---

# 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/gum/code/standard-visuals/coloredrectangleruntime.md?ask=<question>&goal=<user_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.