Loading a Gum Project (Optional)
Gum projects can be loaded in a game project. Gum projects are made up of multiple filesincluding:
.gumx - the main Gum project
.gusx - Gum screen files
.gucx - Gum component files
.gutx - Gum standard element files
.png - image files
.fnt - font files
You are not required to use the Gum tool or .gumx projects - you are free to do everything in code if you prefer. Of course using the Gum tool can make it much easier to iterate quickly and experiment so its use is recommended.
Creating a Gum Project
Before creating a Gum project, it is recommended that you already have a functional MonoGame project with a Content folder.
If you haven't already downloaded it, you should down the Gum tool. See the Introduction page for information on downloading Gum.
To create a Gum project:
Open the gum tool
Select File->Save Project
Navigate to the Content folder of your game. If desired, create a sub-folder under the Content folder
Save the project - this will save multiple files under the Content folder
Adding the Gum Project Files to Your .csproj
To add the files to your .csproj:
Open your .csproj file in a text editor
Add a line to copy all files in the Gum project folder including the .gumx file itself. For an example, see the .csproj file for the MonoGameGumFromFile project: https://github.com/vchelaru/Gum/blob/0e266942560e585359f019ac090a6c1010621c0b/Samples/MonoGameGumFromFile/MonoGameGumFromFile/MonoGameGumFromFile.csproj#L37 Your .csproj may look like this:
Verify that all gum files (see the extension list above) are marked as Copy if newer in Visual Studio
The example above copies the entirety of the content folder to the output folder by using wildcards. If you do not want every file copied over, you can be more selective in what you copy by including only certain file types. For more information about wildcard support in .csproj files, see this page on how to include wildcards in your .csproj:
Loading a Gum Project
To load a Gum Project:
Open Game1.cs
Modify the Initialize method so that it has the following lines after initializing SystemManagers:
Note that the ToGraphicalUiElement method has an addToManage
parameter which determines whether the GraphicalUiElement is added to managers. If a GraphicalUiElement is not added to managers, it will not appear on screen.
Alternatively, the AddToManagers method can be explicitly called as shown in the following code:
For an example of a Game1.cs file which loads a project file, see the MonoGameGumFromFile: https://github.com/vchelaru/Gum/blob/0e266942560e585359f019ac090a6c1010621c0b/Samples/MonoGameGumFromFile/MonoGameGumFromFile/Game1.cs#L76-L82
Note that calling ToGraphicalUiElement creates a GraphicalUiElement (Gum object) from the first screen. You can inspect the gumProject.Screens file and select which screen you would like to create if your project has mutliple Screens.
You can access elements within the screen by accessing the GraphicalUiElement that is created, as shown in the following code:
A full Game1 class which loads a project might look like this:
Gum Projects in Different Folders
The code above and most samples in the Gum repository assume a Gum project located in the Content folder. If you are placing your Gum project in a subfolder, you need to set the FileManager.RelativeDirectory
to the sbufolder prior to calling ToGraphicalUiElement
. For example:
For a more detailed discussion on file loading and file locations, see the File Loading page.
Troubleshooting Gum Project Loading
If your Gum project load results in an exception, you can inspect the exception message for information about the failure. The most common type of failure is a missing file reference.
If you are missing files, you may have not set up the file to copy to the output folder. The following screenshot shows an incorrect setup - the CardInstance.gucx file is not copied, but it probably should be:
This can be changed to copy in Visual Studio, or the .csproj can be modified to include wildcards for copying files over, which can make maintenance easier as the project grows. See the section above for information and examples on setting up your project loading.
Last updated