cocos2d for iPhone

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

1. 

   RelicaGames
   Member

   @abitofcode, thanks for the help, I really should have thought to check to make sure dealloc was being called! I guess I just figured it was because I was getting the errors in the dealloc method when I tried to release some of those other objects. But anyway, it's working now, I wasn't actually calling release on the ropes, as I guess I thought they would be released when removed from my array!

   But I still don't understand what's going on with, for example, this bit:

   for(int i=0;i<numPoints;i++) {
   	CGPoint tmpVector = ccpAdd(pointA, ccpMult(ccpNormalize(diffVector),multiplier*i*(1-antiSagHack)));
   	VPoint *tmpPoint = [[VPoint alloc] init];
   	[tmpPoint setPos:tmpVector.x y:tmpVector.y];
   	[vPoints addObject:tmpPoint];
   }

   Why does tmpPoint not need releasing after calling alloc and init. Or is it because its a subclass of NSObject, and this is returning an autorelease object?

   Thanks again for the help though!

   Posted 11 months ago #
2. 

   abitofcode
   Moderator

   Weird, adding an object to an array ups its retain count by 1, removing it reduces it by one. As the object above is not autoreleased it should be released after being added to the array so that its retain count becomes 1. The object would then be released when the array is released as it sends a release to each of the objects within it.

   Does adding the release cause it to crash?

   Posted 11 months ago #
3. 

   RelicaGames
   Member

   Yes I thought that was how it should be, but yes adding a release after its been added to the array causes an error here:

   -(void)dealloc {
   	for(int i=0;i<numPoints;i++) {
   		[[vPoints objectAtIndex:i] release];
   		if(i!=numPoints-1)
   			[[vSticks objectAtIndex:i] release];
   	}
   	[vPoints removeAllObjects];//Error on this line! - SIGABRT
   	[vSticks removeAllObjects];
   	[vPoints release];
   	[vSticks release];
   	[super dealloc];
   }

   Specifically, the error is:
   malloc: *** error for object 0x615eb10: pointer being freed was not allocated.

   But not having the release after its been added to the array works fine, and there are no longer any leaks according to instruments. So I find this very confusing!

   Posted 11 months ago #
4. 

   abitofcode
   Moderator

   -(void)dealloc {
   	[vPoints release]; // this will send a release to all objects within the array
   	[vSticks release]; // this will send a release to all objects within the array
   	[super dealloc];
   }

   Posted 11 months ago #
5. 

   RelicaGames
   Member

   Ahh yea that works, so really there's never any need to remove all objects before releasing! Thanks for the help! And thanks @patrickC for this rope class!

   Posted 11 months ago #
6. 

   cocos2der
   Member

   I don't really follow whats happening in the createRope, resetWithPoints, updateWithPoints and updateSprites of the Rope.mm class. could someone please help me.

   Posted 3 months ago #
7. 

   flightless
   Member

   hi,

   we’re using a modified VRope 0.4 in our latest game (Bee Leader, http://www.flightless.co.nz/beeleader) so we’ve put the changes up on github at https://github.com/mb1/VRope.

   Changes include initialising a rope using a b2RopeJoint (instead of two bodies, allows for more flexible anchor points), allowing for changing gravity, and a retina fix (tested on iPhone4s and iPad 3).

   There’s still some testing, cleanup and other changes to be done, but it's working well. Thanks to @patrickC for the original code and tutorial.

   cheers,

   // greg
   greg@flightless.co.nz

   Posted 1 month ago #
8. 

   mobilebros
   Moderator

   @flightless - The link to your game does not work, did you mean http://www.flightless.co.nz/projects/bee-leader/

   Posted 1 month ago #
9. 

   flightless
   Member

   @mobilebros yep, thanks. The forum code grabbed the closing bracket ) and applied it to the link :)

   Posted 1 month ago #

RSS feed for this topic

Reply

You must log in to post.