> For the complete documentation index, see [llms.txt](https://docs.imerit.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.imerit.net/labeling/labeling-editor-interface/medical-labeling-editor/fill-between-slices.md).

# Fill Between Slices

Fill Between Slices allows you to fill in the content between brush traces with a single click.

<figure><img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2FQwzevV536x2nCg3EmlsN%2FKapture%202024-12-11%20at%2015.04.11.gif?alt=media&amp;token=4913cb32-19ae-46d4-895d-aacc5d6bd101" alt=""><figcaption></figcaption></figure>

## How to use Fill Between Slices

1. Ensure no classes are selected.
2. Click on the *Fill Between Slices* icon in the top bar. (<img src="https://3895963154-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTcOUG6rfWxqGM0N4db2P%2Fuploads%2F1R2RqCAOJ7Hy29vmjntS%2Fimage.png?alt=media&amp;token=bcedb828-cb0d-4ae1-9155-c06c0da3547b" alt="" data-size="line">) Ango Hub will calculate the areas that will be filled. The areas to be filled will be displayed in a pink color.
3. Click on "Apply" if you wish to apply the changes, or exit the Fill Between Slices function to cancel.

While Ango Hub is calculating or applying Fill Between Slices, the Fill Between Slices and Apply controls show a loading state and cannot be clicked again. Wait for the operation to finish before changing slices or continuing to edit.


---

# 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.imerit.net/labeling/labeling-editor-interface/medical-labeling-editor/fill-between-slices.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.
