GPGT Chapter 3 - Issues and Questions

#21 Just a note for anyone in Windows, I found the file in 3.14.8 in C:\MazeRunner\example\prototype\client\init.cs

I may have set it up a bit different from everyone else, but I found this way works best for me. Anyway, the script you need to add is in this section:

// Load up the shell GUIs
exec("./ui/mainMenuGui.gui");
exec("./ui/QuitGui.gui");
exec("./ui/aboutDlg.gui");
exec("./ui/startMissionGui.gui");
exec("./ui/joinServerGui.gui");
exec("./ui/loadingGui.gui");
exec("./ui/endGameGui.gui");
exec("./ui/optionsDlg.gui");
exec("./ui/remapDlg.gui");
exec("./ui/StartupGui.gui");
exec("./ui/MyFirstGui.gui");

The script added is on the very bottom.

Edit: I wanted to add that the small bug with the mouse cursor leaving "trails" of sorts is still present. I haven't seen any fix for this in this section yet.

#22 @Chris
This problem was fixed by using pushDialog instead of setContent in the main menu button. The post is about half way up this page. However when I did this it DID get rid of the trails, but now the button doesn't work and the window clears itself when I try to exit using the little X in the window. The button worked when I had setContent in the command box, but stopped working when I changed it to pushDialog. It seems like there is a bad end to both fixes. Any help with this? I am using windows Vista (no choice..T_T lol).
EDIT: I've fixed the problem. It all depends on the open and closing commands for the buttons and windows. I compared my new GUI to the options dialog GUI and made mine similar to it. This worked out very well for me!