> 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/gum/adding-screens-to-glue-screens.md). # Adding Gum Screens to FlatRedBall ### Introduction Many games include a Gum screen for every FRB screen. Gum screens can be used for UI such as buttons and textboxes (usually using FlatRedBall.Forms) or can be used for read-only UI such as score and health display. Screens can be added in a variety of ways, depending on the state of your project. ### Automatic Gum Screen Addition on New FRB Screen If you have an existing project which already has a Gum project, then by default your project will receive a new Gum screen any time you add a new FRB screen.
This behavior is default, and it can be controlled by selecting the .gumx file. ![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-6bbcd3de3b5c1e563a9f5eb24d74bb459243053e%2F2021-05-img_609d5c7e6a6e3.png?alt=media) ### Adding New Gum Screens to Existing FRB Screens If you have a FRB screen which does not have an associated Gum screen (for example, if the Screen was created before adding Gum to your project), then you can tell FRB to add a new Gum screen. To do this, select and right-click on the screen, and select the option to create a new Gum screen. ![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-8e98f0583d070f65cd1a85824737e3412cd1f2e3%2F2021-05-img_609d5d0248fe5.png?alt=media) This option will create a new Gum screen and add it both to your Gum project and to the current FRB screen. FRB follows the standard naming convention by appending the word "Gum" to your FRB screen name. ![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-eddbb1e3fe8571a16453ea2cb462c1e88df56537%2F2021-05-img_609d5d335f9a9.png?alt=media) ### Adding an Existing Gum Screen to an Existing FRB Screen If your project already has a Gum screen and a FRB screen and you would like to add the Gum Screen to the FRB screen, you can right-click on the Files and select the option to add the screen. ![](https://951240982-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M_fye9Ufg3vzJxwX5Hk%2Fuploads%2Fgit-blob-faba1779a3bed9e42ad759baa1dd2f7bf9776655%2F2021-05-img_609d754e5fb91.png?alt=media) --- # 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/gum/adding-screens-to-glue-screens.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.