I basically just create the dealloc in the singleton the same was as I would in any other class. Because my singletons should exist as long as the game is running I don’t explicitly call it, as I never want to remove the singleton.

When the game is done then everything just gets removed along with anything else that was still being used.

Hope that makes sense.

Mike

The dealloc is never explicitly called, so my assumption was it happens by itself when its no longer in use, or maybe when the program shuts down. I was checking some cleanup code in the dealloc, and I realized that the debugger never seems to get there and the code never seems to run.

Should I be explicitly calling this at some point?
thanks!
-Kristian

Thanks again for these tutorials. You’re doing me and everyone else a great service.

I’ve been following your tutorials and just now noticed you have a CGRect “screenBounds” in the EAGLView.h.

When was this implemented? How is this used? I’m not quite sure how I missed this.

Thanks for the help Mike.

First of all, thanks for another excellent tutorial. ;)

And now a quick question: why is it that you do not deallocate the sharedGameStateInstance variable?

Maybe because there can only be one instance of this variable and, therefore, when you do [super dealloc] you are deallocating everything inside this class, sharedGameStateInstance included? But I’ve read everywhere that every time you allocate something you should deallocate it too…

In any case, if you did not intend to include this variable in the deallocation method, why rewrite it?

Thank you in advance for your answer. :)

Rober

Mike