cocos2d for iPhone

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

1. 

   raegtime
   Member

   hi,

   i tryed to create a own GUI component with cocos 2d... i haved written a class (extends Sprite) ... this class initialize with graphics and a lable... if I create an instance of my class .. i can see my component but i can user any functions... i wrote a setLabel function .. but the lable change...

   i create a instance with this code:

   drop1 = [DropDown init];

   //here I call the function but it dont works :-(
   [drop1 setCaption:@"Produkt"];

   ///dropDown.m:

   #import "DropDown.h"

   @implementation DropDown

   @synthesize captionLbl;
   + (id) init
   {
   if( (self=[super init] ))
   {
   return [[[self spriteWithFile:@"menue_dropdownbtn.png"] addChild:[[self alloc] initActiveState]] addChild:[[self alloc] initLabel]];
   }
   }

   - (id)initActiveState
   {
   activated = [Sprite spriteWithFile:@"menue_dropactiveated.png"];
   [activated setAnchorPoint:ccp(0,0)];
   [activated setPosition:ccp(173,0)];
   [activated setVisible:NO];
   return activated;
   }

   - (id)initLabel
   {
   captionLbl = [Label labelWithString:@"Text" fontName:@"Arial" fontSize:14.0f];
   [captionLbl setAnchorPoint:ccp(0,0)];
   [captionLbl setPosition:ccp(10,5)];
   [captionLbl setRGB:0 :0 :0];
   return captionLbl;
   }

   - (void)setCaption:(NSString*)text
   {
   [captionLbl setString:text];
   NSLog(@"Hallooooo");
   }

   - (void)activate
   {
   [activated setVisible:YES];
   isActive = YES;
   }

   - (void)deactivate
   {
   [activated setVisible:NO];
   isActive = NO;
   }

   @end

   // DropDown.h
   //

   //

   #import <Foundation/Foundation.h>
   #import "cocos2d.h"

   @interface DropDown : Sprite
   {
   BOOL isActive;

   @private
   Sprite* activated;
   Label* captionLbl;

   }

   @property (nonatomic, retain) Label* captionLbl;

   + (id) init;
   - (id)initActiveState;
   - (id)initLabel;
   - (void)setCaption:(NSString*)text;
   - (void)activate;
   - (void)deactivate;
   @end

   Posted 10 months ago #
2. 

   shazbox
   Member

   Your init function confuses me a lot. Why not use more than 1 step to initialize and return?

   Posted 10 months ago #
3. 

   pabloruiz55
   Member

   I don't quite understand either... It seems you are allocation your object 2 times inside the init function.

   i think a more apropiate way would be:

   drop1 = [[DropDown alloc] init];
   ---------------------------------

   @implementation DropDown
   

   @synthesize captionLbl;
   - (id) init
   {
   if( (self=[super init] ))
   {
     And here initialize your sprites, labels,etc...
     You should have an Sprite instance variable, a Label instance variable, and so on... in your class.
   
     Then:
       captionLbl = [self initLabel]; (i would change the functions name so you don't misunderstand them as constructor functions, since these aren't)
   }
   return self;
   }

   Posted 10 months ago #
4. 

   chrisco
   Member

   Hi raegtime,

   A couple of things:

   1 - It looks like you're subclassing Sprite. You might find it easier to subclass CocosNode and add the Sprites representing various states to that node.

   2 - Whenever you call -init, it needs to be preceded with -alloc. So "drop1 = [DropDown init];" doesn't work, but "drop1 = [[DropDown alloc] init];" in theory, would.

   3. You've changed your init method to a class method (+). Actually, I'm a little surprised that the compiler doesn't throw a warning (or error) when then happens. Try reworking your init method like this (note: use a "-" and not a "+"):

   - (id)init {
   
       if (self = [super init]) {
          // code that creates a Sprite to represent your non-active state and adds it as a child to self
          // code that creates a Sprite to represent your active state and adds it as a child to self
          // code that creates your label and adds it as a child to self
       }
       return self;
   }

   I hope this makes sense - I'm at work, so don't have a lot of time to get to in depth...

   Posted 10 months ago #
5. 

   raegtime
   Member

   @Chrisco... thx it works :-) ...

   Posted 10 months ago #
6. 

   chrisco
   Member

   Great :)

   Posted 10 months ago #
7. 

   smendrick
   Member

   I am also trying to do create my own custom subclass of a CocosNode with:

   - a background sprite
   - an overlay sprite
   - a selected state sprite

   I'm loading the sprites from a sprite sheet and using AtlasSpriteManager and I don't know how to add the sprites and the label as a child to self when I also need to add the sprites as a child to the sprite manager.

   Do I need to do both? Sorry very confused. Can anybody help explain this to me or offer any suggestions?

   Thanks

   Posted 10 months ago #
8. 

   smendrick
   Member

   Found this in the MenuItem class:

   /** MenuItemAtlasCocosNode<CocosNodeRGBA> accepts AtlasCocosNode<CocosNodeRGBA> objects as items.
   The images has 3 different states:
   - unselected image
   - selected image
   - disabled image

   Limitations:
   - AtlasSprite objects can only have as a parent an AltasSpriteManager
   - So they need to be added twice:
   - To the Menu
   - And to the AtlasSpriteManager
   - To respect the menu aligments, the AtlasSpriteManager should have the same coordinates as the Menu
   @since v0.8.0
   */

   Still confused but I think I'm getting closer.

   Posted 10 months ago #
9. 

   Mark
   Member

   There is an example in MenuTest.m that should show you how to use an AtlasSprite like you want..

   Mark

   Posted 10 months ago #

RSS feed for this topic

Reply

You must log in to post.