rbonner
Member
Hello all,
Is there a way to control the ordering of the images in an atlas?
I have the files labeled 001, 002, etc, but when I look at the XML, the order is not defined. Would not care, but when I load the SPMovieClip, it appears to load in the order the files loaded in the XML.
Thanks in advance!
Rob
baike
Moderator
I think the initWithFrames method requires very specific file naming. It needs to be like:
walk_00.png
walk_01.png
walk_02.png
...Replacing walk with whatever best describes your animation. And then you just use:
atlas texturesStartingWith:@"walk_"and it will fill the MovieClip in ascending order.
baike
Moderator
The only thing I can think of is that localizedCaseInsensitiveCompare is not sorting your frames correctly (in SPTextureAtlas.m texturesStartingWith:). Or maybe it's not sorting them at all (selector not available?). Or maybe your localization settings do no match your file names and so its sort is counterintuitive? I'll defer to Daniel beyond that.
Edit:
After looking at SPTextureAtlas.m it seems I was wrong about the strict naming convention. As long as the names have a common starting sequence (that is the same name you pass to texturesStartingWith:), then they should be sorted in alphanumeric order. I guess Daniel mentioned the _00..._01 method as it's easier to explain and removes possible confusion.
Rob, could you post the exact code you are using to create the movie?
In principle, it should work as baike describes it! You have a common prefix for all files and a number (with leading zero) as a suffix. The "texturesStartingWith:" method should then return the textures sorted alphabetically. The order of the files in the atlas xml is irrelevant.
rbonner
Member
Sure:
atlas = [SPTextureAtlas atlasWithContentsOfFile:@"characters.xml"];
characterModes = [[NSArray alloc] initWithObjects:
@"cheer_lime",
@"hop_lime",
@"blink_lime",
@"shock_lime",
@"cheer_cherry",
@"hop_cherry",
@"blink_cherry",
@"shock_cherry",
@"cheer_grape",
@"hop_grape",
@"blink_grape",
@"shock_grape",
@"cheer_lemon",
@"hop_lemon",
@"blink_lemon",
@"shock_lemon",
@"patched_",
nil] ;
for(NSString *s in characterModes){
NSArray *frames = [atlas texturesStartingWith:s];
SPMovieClip *m = [[SPMovieClip alloc] initWithFrames:frames fps:25];
m.name = s;
m.visible = NO;
[m setLoop:NO];
[m setCurrentFrame:0];
[self addChild:m];
[m release];
}
rbonner
Member
And a bit of the XML:
<TextureAtlas imagePath='characters.png'>
<SubTexture name='patched_04' x='0' y='0' height='72.0' width='72.0'/>
<SubTexture name='patched_00' x='0' y='73' height='72.0' width='72.0'/>
<SubTexture name='patched_03' x='0' y='146' height='72.0' width='72.0'/>
<SubTexture name='patched_02' x='0' y='219' height='72.0' width='72.0'/>
<SubTexture name='patched_01' x='0' y='292' height='72.0' width='72.0'/>
<SubTexture name='cheer_lime_0019' x='0' y='365' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0010' x='0' y='430' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0009' x='0' y='495' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0008' x='0' y='560' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0007' x='0' y='625' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0006' x='0' y='690' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0005' x='0' y='755' height='64.0' width='48.0'/>
<SubTexture name='hop_lime_0004' x='0' y='820' height='64.0' width='48.0'/>
It's really odd that this doesn't work. I can see no problem with the code above! Could you do me a favor and step with the debugger into the "texturesStartingWith:" method and see if the sorting of the names works there? You could also create a small project which showcases the problem and send it to me, so I can have a look at it.
I'm still curious why it didn't work with the original code, as this should order the texture names just the same. The difference is that "localizedStandardCompare" does not need leading zeros, so even images like that:
frame1
frame2
...
frame10
frame11would sort correctly, while "localizedCaseInsensitiveCompare" needs the names like this:
frame01
frame02
...
frame10
frame11I'd love to use "localizedStandardCompare", but it's only available in iOS 4, and I don't want to lose compatibility with iOS 3 for such a minor feature.
Has anyone else encountered problems with the current implementation of "texturesStartingWith:"? It works just fine in all of my tests.
You must log in to post.