# Constructor

### Introduction

The Screen constructor is intentionally generated by Glue to have no arguments. However, the constructor should never be explicitly called in your game's custom code. In other words, you will never "new" a Screen in your custom code. Screens are instantiated by the ScreenManager and base Screen class using a variety of methods, but usually through StartAsyncLoad and MoveToScreen.

Just like [Entity constructors](https://github.com/flatredball/FlatRedBallDocs/blob/main/frb/docs/index.php), the limitations on Screen constructors essentially means that you cannot pass custom information to the Screen's CustomInitialize method through the constructor. Fortunately, there are a number of ways around this.

### Using GlobalData

The most common approach to providing information to Screens which may be used in the Screen's CustomInitialize method is through GlobalData. For a discussion on GlobalData, see [this article](https://github.com/flatredball/FlatRedBallDocs/blob/main/frb/docs/index.php#GlobalData).

### Additional Information

* [How are Screens Created?](https://github.com/flatredball/FlatRedBallDocs/blob/main/frb/docs/index.php)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.flatredball.com/flatredball/glue-reference/screen/glue-reference-screen-constructor.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.