How to change the Sprite Image after it has been Created

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

How to change the Sprite Image after it has been Created

(8 posts) (5 voices)

Started 1 year ago by Wayfarer
Latest reply from Picoly

Tags:

Wayfarer
Member

Sorry for continuously asking questions, but I feel that a lot of the documentation is out of date, or I'm looking in the wrong spots... so if anyone has pointers for good documentation, that'd be nice too!

But I'm wondering how do I change the image on my sprite after I create it? I use CCSprite to make it and display it to the user, but after an event occurs, (doesn't matter what event) how do I tell the sprite, "Okay, now use this image instead of the other one?"

Also, for my purposes it would be best to implement this as a instance method of my custom class, which inherits from CCSprite.

Thanks for the help!

Posted 1 year ago #
Wayfarer
Member

Hmm, there is a "setTexture" method which will do it.

CCTexture2D *selected = [[CCTextureCache sharedTextureCache] addImage:@"test3.png"];
[self setTexture:selected];

However, I read that: "The TextureMgr is better, it will ensure the image only gets loaded once. Your route will load the image as many times as you do that." However, I'm not sure how to implement that, how do I do it?

Posted 1 year ago #
Lam
Member

CCTextureCache is the new name for TextureMgr so what you've done is exactly how you'd need to set a texture and it will be in the cache (or cashay like someone once said but I think they're weird)

Posted 1 year ago #
moby
Member

What if the sprite was initialized from a spritesheet and the new texture needs to come from the spritesheet. how do you get to a texture in a spritesheet? for example: with zwoptex i created an atlas that included a frame called "ghost.png" and one called "deadghost.png".
the sprite's texture needs to change to deadghost, but i don;t want to load it from a filename, since it only exists in my texture atlas.
is this possible?

Posted 1 year ago #
Lam
Member
Since the texture spritesheet is the same, the only real change is the rectangle from the ghost.png key in the plist, you just need to update the texture rectangle coordinates.
```
-(void) setTextureRect:(CGRect) rect;
```
Posted 1 year ago #
moby
Member
fyi - i ended up using setdisplayframe which enabled me to grab the rect in a more sane way (by name rather than coordinates) and it worked. so the code looks something like this:
```
CCSpriteFrame *frame = [[CCSpriteFrameCache sharedSpriteFrameCache] spriteFrameByName:@"deadghost.png"];
[thisSprite setDisplayFrame:frame];
```
Posted 1 year ago #
JoeStrout
Member

I just went through this same discovery period, trying to piece together things about "atlases" and "sprite sheets" and "frame cache" and all that. I think I finally got it figured out, thanks in part to this thread. If I'm right, CCSpriteSheet and CCSpriteFrameCache are the new, preferred way of managing multi-frame sprites; anything talking about an Atlas is old (deprecated?) stuff.

The new stuff isn't all that hard to use either, once you find the magic words. I found the SpriteTest in the cocos project to be a bit confusing to follow, though, so I made my own simpler example, and stuffed the key bits into the relevant part of the wiki:

http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:animation#using_sprite_sheets

Hopefully this will prove useful to the next guy. (And for the experienced gurus here: please look it over to make sure I haven't goofed it up!)

Posted 1 year ago #
Picoly
Member

I was confused too in the beginning because I never had any experience in game design. So the words Atlas, Sheet, FrameCache etc. where totally new to me.

Thanks for your link, it's so much clearer now for me.

Juergen

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.