Deortuka

Personally, I believe there is a widespread misconception that everything must be wrapped in a class when programming in C++. I try to stick to the keep it simple philosophy which is to simply keep things as simple as possible, but not any simpler. Singletons are a completely over-engineered version of a global variable. I avoid the use of singletons by creating a file-scope variable that is accessed via a method. It is a clean and simple solution. As for your dilemma, I recommend this approach in order for you to get a reference to the manager (although I prefer to pass references as parameters to the methods that need them whenever possible).

Thanks for the tip unbird!

I sucked it up and just learned how to use Git from the console. Everything works fine that way. Thanks for the advice.

You can view all resources from within the graphics debugger. It seems that textures are accessed by an ID number (i.e. obj:21) and I am not aware of a way to actually watch or name a texture. You can click on Object Table view and scan for the texture that has the right format, height, and width, or, if you create or bind it a specific point, you can locate the the link to the texture in the Event List. Once you find the texture, just click on the ID number (i.e. obj:21) and the texture will open up as a *.dds image.

The link works for me. The error I am getting is "Value was either too large or too small for an Int32." I find this strange because all I have done is right click on the branch and click the switch option.

I do not use Git from the console because I do not know any commands for it; I have never used Git before. Also, being able to commit, branch, and merge from within Visual Studio is sufficient for me. That may sound foolish for those who do use Git from the console, but, for me, using the console is only an option when I am working on Linux.