I did the same thing. Works well.

Hmm, I just implemented my own solution.
Inside some arbritrary tick method define the x & y coordinates with arc4random,
then shake the desired layer (self)...
if (isShaking){
float randx = (arc4random() %1) - 0.5;
float randy = (arc4random() %1) - 0.5;

[self position].x = randx;
[self position].y = randy;
}
else {
//Return camera//CCFollow to target
}

Yes, a CocosNode by default has a contentSize of (0,0).

OK, I've definitely answered it myself this time... for anyone else having problems:

You need to define the width and height of the CocosNode even if you add child objects to it before the scale will work properly with setAnchorPoint.

To do this, use the setContentSize method.

Thanks.

I thought I might have answered my own question but alas, setting [_gameBoard setAnchorPoint:ccp(0.5f, 0.5f)]; AFTER I have added children to the _gameBoard still makes no difference :o(

Hi all, I'm using 0.8.2.

I've created a CocosNode:

_gameBoard = [CocosNode node];

Then added that node to the scene:

[self addChild:_gameBoard];

After this, I've added a number of child sprites to _gameBoard.

My main issue is that when I use _gameBoard.scale = 0.5f; the scale effect occurs from bottom-left of the iphone screen. I need to scale from the middle of the _gameBoard.

I've tried:

[_gameBoard setAnchorPoint:ccp(0.5f, 0.5f)];

With no success.

Any ideas guys?

Many thanks!

I have two sprite subclasses, enemysprite and playersprite, and animations are defined within these classes.

Sprite manager just calls the relevant animation on the sprite object. I store sprite pointers in an NSMutableArray within sprite manager and have a scheduled method to loop through the array.

You can call the animation from outside the layer, i mean for example from another layer which has a reference of the other layer, so you can do [otherLayer->layer->sprite runAction ...]

I think the animations have to be added to the sprite you want to call the animation for. i don't know if adding the animation to the sprite manager will work. (which i undertand you are doing)

I have a sprite manager cocosnode which is suposed to control enemy actions and animations. Sprite manager gets added to game layer as a child. When trying to call animations on sprite objects they fail to run and the conditions state they must run. Can you call an animation from outside a layer or does it have to be called from within it?

Thanks

Actually, decided to set up a repository for this sort of stuff, so I can retain older versions of things while improving them to new ones. :)

http://anny.fm/c/iphone/cocos2d/TouchableSprite/

Hi, thanks for the input. My TouchableSprite isn't mean for use in gameplay, it was more a learning experiment, and one that I believe has been useful in familiarising myself with TouchDispatcher.

The reason I use functions named tsTouchBegan etc. is so I can keep the TargetedTouchDelegate protocol functions in the TouchableSprite superclass and override tsTouch* functions in children. This way, I don't have to repeatedly write out the ccTouchBegan etc. functionality which checks hit testing; if I create a TouchableSprite it becomes automatically able to detect touches on itself and not elsewhere, very simple. More than anything, this class is meant for convenience rather than flexibility.

You make a fair point re BOOL allowTouches though, and I'll add that in when I upgrade the class at some point. I will also add functionality to detect different shapes for the object. I'll also write a version for AtlasSprite, but I don't expect that to be terribly complex.

Thanks!

I basically extend atlasSprite class to my own and add the touchdispatcher stuff there.

I found using a touch radius detection was very fast.
I then moved it to another class I call GridPoints.
Since my sprites jump around from point to point, in my game this made it easier.

You need these things for your own TouchableThing class:

//Need to adhere to this protocol

@interface GridPoint : CocosNode <TargetedTouchDelegate>

//I use touch radius to "test" the touch area - property
CGFloat touchRadius;

//An on off flag is useful to speed up touch dispatcher processing, but keep it in the dispatcher list
BOOL allowTouches;

//Then do this stuff in the class implementation

- (void)onEnter
{	//NSLog(@"inner onEnter ...");
	if(self.touchRadius > 0.0f){

		[[TouchDispatcher sharedDispatcher] addTargetedDelegate:self priority:0 swallowsTouches:YES];
	}

	[super onEnter];
}
- (void)onExit
{
	if(self.touchRadius > 0.0f){
		[[TouchDispatcher sharedDispatcher] removeDelegate:self];
	}
	[super onExit];
}	

//The touch calls
- (BOOL)ccTouchBegan:(UITouch *)touch withEvent:(UIEvent *)event
{

	//if (self.SpawnPoint) return NO;

	CGPoint touchPoint = [touch locationInView:[touch view]];
	touchPoint = [[Director sharedDirector] convertToGL:touchPoint];

	//NSLog(@"inner grid ccTouchBegan ...");
	//NSLog(@"touchpoint.position:%f , %f", touchPoint.x, touchPoint.y);
	//return NO;

	if ([self containsTouchLocation:touchPoint]) {

		// code here is only executed if obj has been touched
		//NSLog(@" I GOT TOUCHED on the sprite");
		originalTouchPoint.x = touchPoint.x;
		originalTouchPoint.y = touchPoint.y;
		//NSLog(@" originalPoint x:%f, y:%f", originalPoint.x, originalPoint.y);
		return YES;

	}

	return NO;
}

- (void)ccTouchMoved:(UITouch *)touch withEvent:(UIEvent *)event
{
	// If it weren't for the TouchDispatcher, you would need to keep a reference
	// to the touch from touchBegan and check that the current touch is the same
	// as that one.
	// Actually, it would be even more complicated since in the Cocos dispatcher
	// you get NSSets instead of 1 UITouch, so you'd need to loop through the set
	// in each touchXXX method.

	//	NSLog(@"inner sprite ccTouchEnded ...");

	//Use for move stuff

}

- (void)ccTouchEnded:(UITouch *)touch withEvent:(UIEvent *)event
{
	CGPoint touchPoint = [touch locationInView:[touch view]];
	touchPoint = [[Director sharedDirector] convertToGL:touchPoint];

	int direction = 0;
	//angle: Actually it's ATan2(dy , dx) where dy = y2 - y1 and dx = x2 - x1, or ATan(dy / dx)
	float degrees = CC_RADIANS_TO_DEGREES(atan2(touchPoint.x - originalTouchPoint.x, touchPoint.y - originalTouchPoint.y));

	//NSLog(@"RUNICA OUT: ANGLE:%f", CC_RADIANS_TO_DEGREES(atan2(touchPoint.x - originalTouchPoint.x, touchPoint.y - originalTouchPoint.y)));
	//that is gving me 0-180 and the negative 0-180

      //I was using this to detect angles.  

//DO stuff here

	if (self.ownerlayer != nil) {

           //I call back to my game layer by having a circular reference
		[self.ownerlayer MoveMeCallout:direction thisGridPoint:self];

	}

	//	NSLog(@"self.position:%f , %f", touchPoint.x, touchPoint.y);
}

- (BOOL)containsTouchLocation:(CGPoint)touch
{
	//NSLog(@"containsTouchLocation .checking ......");
	//return CGRectContainsPoint(self.rect, [self convertTouchToNodeSpaceAR:touch]);

	//use radius based
	CGFloat distance = ccpDistance(self.mypos, touch);
	//NSLog(@"containsTouchLocation .checking ....distance: %f", distance);
	//NSLog(@"containsTouchLocation .checking ....in touchRadius: %f", self.touchRadius);
	return (distance <= self.touchRadius);

}

This never happened in debug mode, but in adhoc, I have gotten this both on 3G and 3GS from fresh install of the app, but not everytime. It crashed right after I touched (drag) the game.
I'm not sure what caused this. Any ideas?

Thread 0 Crashed:
0   libSystem.B.dylib             	0x0007e9ac __kill + 8
1   libSystem.B.dylib             	0x0007e99c kill + 4
2   libSystem.B.dylib             	0x0007e98e raise + 10
3   libSystem.B.dylib             	0x0009363a abort + 34
4   libstdc++.6.dylib             	0x000453b0 __gnu_cxx::__verbose_terminate_handler() + 376
5   libobjc.A.dylib               	0x00005858 _objc_terminate + 104
6   libstdc++.6.dylib             	0x00043776 __cxxabiv1::__terminate(void (*)()) + 46
7   libstdc++.6.dylib             	0x000437ca std::terminate() + 10
8   libstdc++.6.dylib             	0x00043896 __cxa_throw + 74
9   libobjc.A.dylib               	0x00004714 objc_exception_throw + 64
10  CoreFoundation                	0x000930c4 __NSFastEnumerationMutationHandler + 124
11  libobjc.A.dylib               	0x000085e6 objc_enumerationMutation + 18
12  BombMine                       	0x00056148 -[CocosNode visit] (CocosNode.m:439)
13  BombMine                       	0x00056170 -[CocosNode visit] (CocosNode.m:441)
14  BombMine                       	0x00056170 -[CocosNode visit] (CocosNode.m:441)
15  BombMine                       	0x00056170 -[CocosNode visit] (CocosNode.m:441)
16  BombMine                       	0x000589f4 -[Director mainLoop] (Director.m:241)
17  Foundation                    	0x0000ccfe __NSFireTimer + 130
18  CoreFoundation                	0x00056bac CFRunLoopRunSpecific + 2112
19  CoreFoundation                	0x00056356 CFRunLoopRunInMode + 42
20  GraphicsServices              	0x00003cb8 GSEventRunModal + 108
21  GraphicsServices              	0x00003d64 GSEventRun + 56
22  UIKit                         	0x00002768 -[UIApplication _run] + 384
23  UIKit                         	0x0000146c UIApplicationMain + 688
24  BombMine                       	0x00002ed4 main (main.m:14)
25  BombMine                       	0x00002e54 start + 44

Blogged it:

http://anny.fm/blog/2009/11/cocos2d-touchablesprite/

It may be that a proper class already exists that does the exact same thing, but at least I learnt a bit about TouchDispatcher from writing out all that. Hope it proves useful to someone!

Created a TouchableSprite class, which seems to work quite well, pending a little testing. I'll get the source up shortly!

Hi again,

Getting pretty comfortable with cocos2d now, but I am having one issue, and some clarification would be appreciated.

I am attempting to load an image and then make it clickable (i.e. using it as a button). However, Class 'Sprite' does not implement the 'TargetedTouchDelegate' protocol. Since this is the case, what exactly implements TargetedTouchDelegate?

FWIW, I have the impression that anything that subclasses CocosNode implements it, I'm just not totally sure. While I'm here, what is a recommended way to implement a button that manages its own touch events?

Thanks

So I suppose it's not feasible to create a texture atlas that can include several different textures?

Then you could have a AtlasSprite manager that holds multiple sheets, perhaps by name. Just to be able to organize the z order.

So yes, i appears as if it involves swapping textures which means swapping OpenGL calls so I assume this is now workable.

try setting as "ready" again.

hi

I've changed the game ready status to true a few days ago for sevens and it still isnt listed in your game section

Hi,

I posted a similar question here as you never see in the samples, the manager being positioned. The manager gets added to self with a z index, and sprites are added to th emanager and positioned - but I haven't found a sample where the manager is explicitly positioned.

http://www.cocos2d-iphone.org/forum/topic/2792

i

The answer to this question, is YES.

Why would you want to do this? Well, it's a convenient solution for compound sprites; Big sprites made up of smaller sprites.

Because it's a CocosNode, you can run actions on it, play with visibility, position etc.

For example, I'll be using it to create moving platforms in my game, made up of individual tiles.

Well, I went ahead with making a sub-class of CocosNode that can take a pointer to any other Cocosnode and 'shake' it.

The NodeShaker class is instantiated by any Scene or Layer (or actually any CocosNode object) and is added as a child so it's scheduler can be called. I didn't want to add it as a child, but that's the only way the scheduler in it was able to be called.

In its test, I passed it a reference to the entire scene (acquired from the director) and the shake works great. No worries about setting positions of sprites, managers or even layers and having conflicts. So far, anyways.

Thank you Detective. However, the implementation of the grid3d, etc - all appears kind of...well...excessive for a simple screen shake. I may just be missing the importance of the effects code that is already included. On the other hand, I just want to move all of the existing graphics for each tick of a scheduled event. I don't have a need for special lenses or waves (although the effects are VERY nice).

Any further suggestions?

Check out the EffectsTest in the cocos2d-iphone project, there is already a shake effect that is probably pretty close to what you're looking for.

I was toying with the idea of how to make a screen shake. At first I thought of having a special class that would take a reference to a scene and then move the position of a whole scene with each tick of its selector.

Then I was reading about the camera - even though I haven't used it yet.

In a single-screen app, the camera sounds about right. A 'Shake' class would move the camera via it's scheduled calls until the shake was complete. Custom patterns could be made in simple CGPoint arrays for speed of processing.

But before I write all this code, is there a screen shake style functionality built-in already? I'd hate to re-invent the wheel. A solid search of the forums turned up nothing.

If it doesn't exist, does my initial design of the class seem good?

Any constructive feedback welcomed!

A MenuItemSprite has three instance variables:

CocosNode<CocosNodeRGBA> *normalImage_, *selectedImage_, *disabledImage_;

I only want to scale this buttonimages, without any labels or other child nodes in the item, but it doesn't work. I tried something like:

[self.normalImage setScaleX:scaleX];

Anyone has an idea? What do I wrong?

I'm glad there is a healthy discussion about this. I have a game where my characters need to change depth. So the easier ideas of just creating x-layers doesn't quite cover this.

Say 2 Managers (sheets)
2 Characters from each
I need one character from manager 1 to be in the back and one to be in the front, sandwiching the others (from manager 2). I do see the technical troubles with all of this. And I do know I could duplicate my manager 1 and create 2 of it to solve the trouble. But my real implementation has 50 from every manager and 10 managers... so a memory impossibility to duplicate managers. In fact, the AtlasSpriteManager is exactly WHAT makes my engine perform since I've only pulled each sheet into memory once.

What can we do to get nearer a solution for mixing z-depth for manager children? I'd hate to leave it at "Cocos2D can't do that, use another engine".

This would work great except if you add an atlas sprite to a tmx layer (an ASM) it only supports 1 tilesheet, the one in the map(or on top of tree, 1 per layer), which means you'd have to embed your player/unit sprite sheet INTO the layer (In Tiled, as you are making the map), then add the atlassprite into the TMXLayer and reference the sheet in the layer for your animations. its a PITA.

Which is too bad, otherwise it would be a really easy solution to the z-ordering drawing issues.

No problem :)

Glad I could help.

Did test with 150 sprites and there wasn't any change in FPS comparing getChildByTag and retained property.

Thanks arian