cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   Jeston
   Member

   I have a question for those objective c gurus. I have an interface with 2 CCRenderTexture's in it, and instead of each instance of this class creating their own textures, I want a static texture at the class level...
   

   // CCMyTransition.h
   @interface CCMyTransition : CCTransitionScene
   {
         BOOL	back_;
         CCRenderTexture* nextTexture;
         CCRenderTexture* lastTexture;
   }

   My Instinct was to just add 'static' in front of my two texture declarations, but this isn't valid.

   For singletons I use a static shared.... property

   What is the appropriate style for doing this in objective c? In the past I just created a static CCRenderTexture* in the .m file [effectively a global] and made static gettor functions, but I feel this is more of a hack than proper OOP style coding. I would appreciate any scrutiny into the practice of using class statics as well...

   Posted 1 year ago #
2. 

   Lam
   Member

   The only way I can think of doing that is either just hold a CCRenderTexture object in a higher calling class from which you can pass the object into during the allocation of these CCMyTransition classes.

   Or making a global static variable which I guess you don't want if you're uncomfortable with that idea.

   Posted 1 year ago #
3. 

   TBBle
   Moderator

   The usual idiom is indeed to make a file-level static variable in the .m file, and reference it from your class methods. What you're creating is two singleton CCRenderTexture objects, really.

   Posted 1 year ago #
4. 

   Blue Ether
   Member

   Just like TBBle said it.

   in CCMyTransition.h:
   

   + (void) setTexture:(CCRenderTexture*)tex;
   + (CCRenderTexture*)getTexture;

   in CCMyTransition.m:
   

   static CCRenderTexture *renderTexture;
   
   + (void) setTexture:(CCRenderTexture*)tex
   {
   [renderTexture release];
   renderTexture = [tex retain]; // no reason to worry about releasing this except during re-assignment, since the static will exist for the duration of the application
   }
   
   + (CCRenderTexture*)getTexture
   {
   return renderTexture;// could alternately have code here to set up the render texture here if it doesn't exist.  depends on your paradigm
   }

   Posted 1 year ago #
5. 

   Jeston
   Member

   Ah thanks all, appreciate the response, The static gettor is precisely what I did

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.