cocos2d for iPhone

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

1. 

   BlueberryPotato
   Member

   Hi everyone,
   I'm working on a boxing game with two players. I just recently started coding for the iPhone, (I have coded in other things before.)
   I need to manage health, rounds, constantly update positions and score. I tried passing variables from the scene to the layer to the fighting classes, but that didn't work. Then I tried using an external class for positions and health etc. The only problem with that is I couldn't pass variables to muliple classes. I have thought about using a singleton, is that the right thing?
   I can't really go any further until I get this worked out.

   Thanks in advance,
   - BlueberryPotato

   Posted 6 months ago #
2. 

   breskit
   Member

   I've used a singleton class with great success for simlar things (score, health, levels, etc).
   Works a treat!

   Posted 6 months ago #
3. 

   bradparks
   Member

   yeah... a singleton's not a bad idea at all....

   here's a post by @slipster216 on how he does singleton's, which I use and think is sweet ;-)

   http://www.cocos2d-iphone.org/forum/topic/2212#post-13916

   Posted 6 months ago #
4. 

   bobueland
   Member

   You could take a look at this tutorial http://bobueland.com/cocos2d/?p=290

   Posted 6 months ago #
5. 

   Birkemose
   Moderator

   Singletons have nothing to do with you problem.

   A singleton is a way to ensure that you only ever create ONE instance of a class. The accelerometer is a good example, as you cant have two of those.

   You problems seems to be sharing data between classes, and that is as I said, a completely different ballgame. There are an infinite number of solutions to this, depending on your needs and programming style.
   My own approach have been to have a world class, to manage all objects in it, and distribute data. Others might prefer a message driven approach, or self aware classes, each accessing the data they need. In any case, having a good OOP structure is essential.

   Posted 6 months ago #
6. 

   BlueberryPotato
   Member

   Thanks, I'll try using a singleton.
   :)

   Posted 6 months ago #
7. 

   BlueberryPotato
   Member

   The singleton worked, it recognized the variable being there. The only problem is I can't figure out where to define the value of the variable.

   Here's my code in Handler.m:

   #import "Handler.h"

   Handler *GlobalHandler =nil;

   @implementation Handler
   @synthesize PlayerHealth;

   -(id)alloc
   {

   self = [super init];
   if (self)
   {

   if (GlobalHandler)
   {
   [GlobalHandler release];
   GlobalHandler = self;
   }
   return self;
   }

   }

   -(id)init {
   self = [super init];
   if (self != nil)
   {

   }

   }

   @end

   Where should I put PlayerHealth = 100; or whatever?

   Posted 6 months ago #
8. 

   clarus
   Member

   This doesn't look like a singleton. In fact, I really don't know what the intention is with this code. Here are some problems/areas of confusion I see right off the top of my head:

   - alloc sets self to [super init] instead of returning a value from [super alloc], which it never calls
   - GlobalHandler is set to self in the alloc method, but only if it already exists. Otherwise it's never set.
   - alloc releases GlobalHandler, but it never calls [super alloc] on the object stored there, so there's no object to release.
   - init doesn't return self.

   I agree with @birkemose. While you might create a handler class that you access through a singleton, a singleton in itself doesn't solve the problem of passing data between different objects.

   >> I tried passing variables from the scene to the layer to the fighting classes, but that didn't work.

   There's no reason it couldn't. Scenes and layers they contain can certainly communicate with each other and depending on how your "fighting classes" and "fighter objects" are set up and accessed, that may be enough to do what you need. If not, you either need to create a separate controller class, or you need to revise your design so everything can reach the objects it needs to without one.

   Posted 6 months ago #
9. 

   hm50
   Member

   You have a lot of work to do in that class above, as @clarus said. I think you'll want to use get and set methods in that class. IE:

   -(int)getPlayerHealth {
      return PlayerHealth;
   }
   -(void)setPlayerHealth:(int)val {
      PlayerHealth = val;
   }

   pseudo code, not at a mac right now.

   Posted 6 months ago #
10. 

    BlueberryPotato
    Member

    I used the link @bradparks gave. I changed the method names and a few things around. No avail. I had the same problem when I used a healthbar object, but I won't use that. I'l use the methods like @hm50 said, I got it to work already in the healthbar, didn't use a get method, probably where I went wrong. Thanks for all your help :)

    Posted 6 months ago #

RSS feed for this topic

Reply

You must log in to post.