cocos2d for iPhone

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

1. 

   almo
   Member

   Hi!

   I'm using Cocos2d 0.8.2. AlmoSprite inherits from Sprite:

   @interface AlmoSprite : Sprite <StandardTouchDelegate>

   I initialize my AlmoSprite like this:

   m_backgroundImage = [[AlmoSprite spriteWithFile:@"SplashUbi_LogoUbi.png"] retain];
   [m_backgroundImage init];
   [self addChild: m_backgroundImage z: 2];

   Later, I do this:

   [self removeChild: m_backgroundImage cleanup:true];
   [m_backgroundImage release]; // retain count is still 1 for some reason
   
   m_backgroundImage = [[Sprite spriteWithFile:@"SplashJeu.png"] retain];

   Dealloc never gets called on the first instance of this sprite. I've checked the retain count, and apparently it's still 1 after doing the release and removeChild. What extra step am I missing to get rid of this sprite entirely?

   I don't have trouble with other sprites that I release during the onExit call on the owning layer, just ones that I try to release while the layer is running.

   Posted 1 year ago #
2. 

   Thort
   Member

   Hi,

   If I understand correctly, spriteWithFile: will create an autoreleased object with a ref count of 1, and addChild: will retain the object (and removeChild: release it), so you don't need to retain/release it yourself in this code.

   If for some reason the autorelease pool is not drained between your two blocks of code, that would account for the issue. (This is surprising to me since AFAIK the pool should be drained in the Run Loop).

   I notice you have a call to init: as well as spriteWithFile:, maybe this is okay, but I think it's bad form, you shouldn't really initialise something twice.

   Posted 1 year ago #
3. 

   almo
   Member

   Ok, you're right that calling init was a bad idea, and I've fixed that. Now I'm getting the sprite to go away as I expect. :)

   But something weird happened when I stopped doing it... the sprites now default to having an anchor point in the middle. But since the anchorPoint property is 0.5, 0.5, that's what should have been happening.

   I don't understand why calling init after spriteWithFile was making the sprite appear to have its anchor point at 0, 0 when the property was 0.5, 0.5. But since I wasn't supposed to be calling init again anyway, it's really only an academic curiosity.

   Someone has asked me before about my habit of calling init after spriteWithFile, but it was with regard to another question and it was not relevant to that, so it slipped through. :)

   The game will be finished soon, but it still will have to pass through the Ubisoft approval process before it goes to Apple. So I don't know how long it will be before it's available.

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.