cocos2d for iPhone

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

1. 

   eemceebee
   Member

   Hi

   I have some trouble with a basic concept. I have my cocos2d stuff working as I want but the problem is in my application logic.

   I have a Layer with several AtlasSprites (Object inherited from AtlasSprite). The user can touch on the AtlasSprite, and now my problem, how can I access information from the layer ? The AtlasSprite needs to know if it is allowed. The touch action is within the AtlasSprite Object, but the Object does only know itself not its word, that information is stored in the Layer.

   Would I pass a pointer of my Layer into AtlasSprites Object or make a Singleton out of my Layer ? Sorry I am kinda lost here how to do this.

   Hope someone can help me out here.

   thx

   Posted 2 years ago #
2. 

   mobilebros
   Moderator

   Well one not so desirable way would be to do something like this in your AtlasSprite:

   Layer *layer = (Layer*)[[self parent] parent];

   I say it's not so desirable because for one you're doing a downcast and two you're relying on something that may not be there.

   Also it'd be parent twice because the first parent is the AtlasSpriteManager and the second would be your layer... presumeably.

   Posted 2 years ago #
3. 

   exorcyze
   Member

   What is it that you need to get out of the layer?

   Depending on how things are structured and what you want to get out of it (IE if it's like game state type stuff), you may have better milage if you have a singleton to track the information. Then the item that stores the current state of everything is separated from all the items that need to get or set that information.

   Just a thought. =)

   Posted 2 years ago #
4. 

   slipster216
   Moderator

   I often prefer extern over the singleton pattern. It's just a lot less verbose and avoids a static function call:

   in MyLayer.h at the bottom of the file

   extern MyLayer* TheLayer;

   in MyLayer.m at the top

   MyLayer* TheLayer;

   Once the layer is created, do something like:

   TheLayer = self;

   Then you can just:

   TheLayer.someProperty from anywhere..

   Posted 2 years ago #
5. 

   eemceebee
   Member

   @slipster216

   Thanks, I guess thats the road I will take. If I understodd correctly I could think of a PropertyManager Object which stores several properties I could use in my application logic. That way I can create it once and have all kind of information accessible by just including the header file.

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.