A fast, easy to use, free, and community supported 2D game engine
BTW, to test I have sprite1 do the following dance:
[sprite1 runAction:[CCRepeatForever actionWithAction:[CCRotateBy actionWithDuration:1 angle:360]]];
[sprite1 runAction:[CCRepeatForever actionWithAction:[CCSequence actions:[CCScaleTo actionWithDuration:0.5f scale:5.0f],[CCScaleTo actionWithDuration:0.5f scale:1],nil]]];
oops...
yes, the algorithm to calculate the transform matrix was very buggy.
added more tests to tests/SpriteTest.m
fixed on r1574.
By the way, although this works for "healthbar" type situations, it actually doesn't let you do a Ferris Wheel setup.
For that you need to be able to say that you respect the rotational position from the parent but not the the rotation itself. Which could be another bit to honor.
-- David
For the Ferris Wheel sprite I suggest doing this:
// pseudo code
class FerrisWheelSprite : CCSrpite
{
// override rotation
def setRotation( newAngle ):
{
super.setRotation( newAngle )
for( child in Children ) {
child.setRotation( - newAngle );
}
}
}I think it should work.
@riq
You changed it so that Spritesheet sprites are allocated differently now... the CCSpriteSheet class factories up a CCSprite for you with the createSpriteWithRect selector.
The problem with this is that if you want to create any custom sprite behavior, such as your example for the FerrisWheelSprite, using a sprite sheet.... the sprite sheet doesn't know how to create those. :/
You can still do it, but it's a rather ungainly thing relative to how it was done before:
(Assuming sheet is the CCSpriteSheet)
FerrisWheelSprte *wheel = [FerrisWheelSprite spriteWithTexture:sheet.textureAtlas.texture rect:CGRectMake(0, 0, 64, 64)];
[wheel useSpriteSheetRender:sheet];My first thought is that allocation of this variant of sprite should be as a factory in CCSprite just like the others are to be orthogonal:
+ (id) spriteWithRect:(CGRect)rect SpriteSheet:(CCSpriteSheet)spriteSheet {
CCSprite* s = [CCSprite spriteWithTexture:sheet.textureAtlas.texture rect:rect];
[s useSpriteSheetRender:sheet];
return s;
}And then.... because the setup of the sprite is a little cumbersome, perhaps a helper method in CCSprite for this so that inherited sprites could easily do the setup without having to understand the internals?
-- David
You must log in to post.