> 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/gum-tool/gum-elements/shape-properties/is-filled.md). # Is Filled {% hint style="info" %} Is Filled is a shape property supported by Circle, Rectangle, ColoredCircle, and RoundedRectangle. {% endhint %} ### Introduction `Is Filled` sets whether a shape is filled in or if it is drawn using *stroke* - another word for outline.

### `Stroke Width` `Stroke Width` sets the thickness of the stroke (outline). Increasing the value makes the stroke thicker. Note that increasing the stroke brings the stroke inward, so the shape is still bound by its effective width and height.

`Stroke Width` controls the thickness of the outline

### Stroke, Gradient, and Dropshadow If a shape element has its `Is Filled` unchecked, this affects the rendering of gradients and dropshadows. Gradients only fill the solid parts of a shape, so if a shape has `Is Filled` set to false, the hollow center of the shape does not show gradient color.

Toggling Is Filled affects the gradient rendering at the center of the shape

Dropshadows respect the opaque part of the shape, so changing `Is Filled` also affects the dropshadow.

Changing a ColoredCircle's Is Filled to false results in the dropshadow having a hollow center

--- # 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/gum-tool/gum-elements/shape-properties/is-filled.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.