Ok I've pushed changes to progress timer into the develop branch on my github. It'll handle rotated sprite frame textures:

https://github.com/LamPham/cocos2d-iphone/tree/develop

I also kept the interface the same across 2.0 and 1.0 so the gles20 branch is also updated

https://github.com/LamPham/cocos2d-iphone/tree/gles20

I've added new tests in the 'develop' branch so you can run ProgressActionsTest.m to check the new logic.

I currently can't compile the 'gles20' branch for ActionProgressTest so I'm stumbling around there and I'm not going to do a pull request until I sort that out. I'm sure though the logic will fix #1303 so it should be safe to check out the code.

@crmagicxxx
Sorry guys I've been out of the loop for a while.
Yeah texture rotation can be fixed up. I'll take a look at that and add push that over to both cocos2d versions.

@TheCodeTroll
Yeah you'll need the lerp function but hopefully you just wrote your own for that.
Just in case through it should look like this.

static inline float lerpf(float a, float b, float t)
	{
		return a * (1.f - t) + b * t;
	}

Ok I'm done now :P just disregarding the math header... wrote my own Lerpf substitute... I'm an idiot for not doing that first.

Yeah turns out Im pretty screwed without CCMath... all day so far has been trying to find a work around =/
Bah wasted day...
If anyone has just that file, I'd appreciate being sent it or something? :/

cheers

@Lam Hey, while you're around, can you please check this issue with progress:
http://code.google.com/p/cocos2d-iphone/issues/detail?id=1303&sort=-id&colspec=ID%20Type%20Status%20Priority%20Milestone%20Component%20Owner%20Summary
Thanks :)

I'm guessing cos i dont have cocos2D 2.0 that the error I'm getting is down to that, or i'm just not very clued up on xcode?
apparently i dont have Support/CGPointExtension.h... i'm getting lexical or preprocessor Issue, from it.

Thanks in advance

Edit: seems i dont have CCMath.h either... hrmph
Edit2: Changed #import "Support/CGPointExtension.h" ->to just #import "CGPointExtension" solved that problem...
Still dont have the math Header though... odd :S will look about...

Edit3: its having a bit of a tantrum at the 'implicit declaration of lerpf' which i assume is because its declared in the math header i commented out.

Edit4: (FINAL EDIT) Looked around as to why i would have these problems, and found that changing #import "CCMath.h" -> to #import <math.h>
And then changing the projects "C Language Dialect" from [-std=GNU99] to [-std=c99] did the trick... hopefully this wont mess upo anything else... O_O
I'm not very clued up on compilers, and low level stuff :/ wish i was

Edit 5: (I LIED) Ok apparently it didnt work, and i am still being implicit :( f*ck sake.. :/ Any help?

hi fcoronel, I had the same problem. when I downloaded the file with .tar.gz, and it won't work(won't come up in Xcode, and can't build tests), and then I chose to download .zip file, it seems perfect.
I don't know why,but it's that so.
I'm also using Xcode4.2.1 with Lion 10.7.2

Hello. I was just wondering how I could install cocos2d. I've tried installing it and for some reason it does not come up in Xcode. Which version of cocos should I should I download for SDK 4.2.1 ? I would really appreciate your help!

hi ayt,thanks for your reply. I double checked the folder and found no "tests" sub-folder founded. so I just downloaded the "zip"file instead of "tar.gz", and everything is ok now.

thank you a lot for that reply haha... yeah had a hunch that it had to do with some inner workings of the way it was drawn?

Will take a look at the class and changes etc...
I really should get around to updating to cocos 2.0 :/ but it would cause probably more hassle for this game than its worth XD

again, thanks Lam

I was also thinking about adding variable delay to the animation system, for making the animated particle extension more useful. Good to see Riq already tackled it, I'll integrate this as well in 1.1.

Yeah sorry about that ... what was I thinking?
I encountered the same thing when trying to use progress timer with Legendary Wars and Monster Wars.

Fortunately I added the ability to use spritesheets with the newest progress timer. Unfortunately I changed a lot of how you would set the progress timer up so I wasn't able to add it to cocos2d 1.0.

The newest CCProgressTimer is added to the cocos2d 2.0 though (but that only supports GLES2.0).

So I'll give you the link to my dropbox account for the time being until things can be sorted out.

http://dl.dropbox.com/u/271717/ProgressTimer2.zip

Lets talk about the major changes:

Instantiation:
+ (id) progressWithSprite:(CCSprite*) sprite;
- (id) initWithSprite:(CCSprite*) sprite;

You can now do that by passing a sprite and that sprite can be from a sprite frame. Note that this is a MAJOR change so REALLY use the new properties to get the right progress look.

I've reduced the progress types to Radial and Bar and you change its look through the new properties I've added.

So lets look at the new properties.
reverse
If you want a counter-clockwise radial indicator then you can set the reverse property rather than setting the type like before. This reverse property allowed me to have a cool effect for bar progress timer types.

midpoint
Midpoint can also change the look of the radial/bar progression. It should usually be at {0.5, 0.5} so the radial looks like a clock. Modifying the midpoint moves the center around.

This is more important for the bar types since we can have more variety by modifying the midpoint. You can now have bar start at the left (0,0), right (1,0), top (0,1), or bottom (0,1). Actually anything in between as well.

barChangeRate
barChangeRate only works on the bar types and what it does is modify the rate that x and y would change due to the percentage.
So if you want a horizontal bar then the bar rate would be {1, 0} which means x will move at the rate of 1 percentage but y can't move at all (since it's 0).
With that kinda idea in mind, we can create a vertical bar like so: {0, 1}.
Or even a weird bar that can move both in the x and y but maybe slower on the y {1, 0.5}

So I had to rewrite CCTransitionRadial.m a bit because of the new changes but that is really a scene transition and the only thing you're really looking at is CCProgressTimer itself.

Feel free to ask or PM me if you have any problems replacing the file.

Hey, so I'm using a progress timer, as a kind of energy /health representation.
And all works very nicely, if i just use a single .png file, right from resources on its own.

But as I'm trying to save space, and keep things together nicely, I'm using sprite sheets for everything.
Which also, is working very nicely. The only problem is I can't get the progress timer to work, AT ALL
With a frame from my tile sheet...

I can initWithTexture, and give it the tile sheet, but as expected it uses the whole sheet as the sprite.
I wrote an init with spriteFrameName method for the CCProgressTimer class,
Where I Init self.sprite with the [CCSprite spriteWithSpriteFrameName: ]; method...
But this doesnt work either, The sprite is returned, as there is data in self.sprite, but it wont draw it.
I also went back and tried it by initialising with a dummy image, and then calling [progressTime setSprite:];
but even calling that and setting it to a sprite that came from the sprite sheet ISNT WORKING :|
is there any reason at all that the class does this / was designed this way O_o?

I apreciate any input help, or advice... thanks :/

Update:

delay units -> delayUnits
delay per unit -> delayPerUnit
restore original frame -> restoreOriginalFrame

and all the files under test menu are marked in red.
This means that it's saved that there are these files in the project but they are not in the project folder.

when I upgrade from v2.0 beta to beta2, things become incredible
All the tests can't build successfully with the following error:

clang: error: no such file or directory: '/Users/eseedo/Documents/cocos2d-iphone/tests/main.m'
clang: error: no input files

and all the files under test menu are marked in red.
how to solve this problem?

I. WANT. NOW.
(Coming from a fan who got 3* on every level :D)

Yeah, you're awaited http://toucharcade.com/2012/02/06/league-of-evil-2-trailer-i-need-this

@riq: Ha ha! It sure does, plays REALLY nice on iCade with iPad 2.

Nice trailer. I want it now! :) Does it also support iCade ?

We got our trailer produced and are super happy with the results. Another awesome Cocos2D game coming out in another week!

http://www.youtube.com/watch?v=ogBm9DVtu5Y

I'm holding out hope due to this post:

I will open source the project when it's ready for prime-time... Right now it's not even close to anything organized... Once I can actually get cocos2d-iphone compiling and running opengles1.1, I'll clean everything up and put it up somewhere..

It's not that I don't want to pay, it's more that I want to do something different with this tech that doesn't relate to Cocos2D, so a game porting service wouldn't help me.

There's also this effort, if anyone's interested: https://github.com/DmitrySkiba/itoa

hey guys, looks like jordo is having some bigger plans with this:
http://www.cocos2d-iphone.org/archives/1774

good for him! cant give everything away. but sounds like they are being a bit more tight lipped with this going forward in regards to open source.

so if you are waiting on an open option to do this, best get cracking on your own.

That TIGSource post is two years old and pretty out of date now. I try to keep things unbiased, but obviously I like Chipmunk a bit better having written it. ;) There was a more recent one here on the Cocos2D forums -> http://www.cocos2d-iphone.org/forum/topic/20201

For a definitely biased comparison (compared to the link in the last paragraph):

I think Chipmunk's API is a lot simpler than Box2D's while also being more flexible. Common things like collision callbacks, raycasts or just creating objects take a fraction as much code in Chipmunk. On the fancier end of features, Box2D doesn't really let you override integration, doesn't really let you adjust constraints to do interesting things, and doesn't provide any sort of "surface velocity" like Chipmunk does. Without the ability to do these things in Box2D, people almost always hack their way to a mostly working solution using impulses instead which often introduces stability issues. (To be fair, I probably need more example code of how to do this though.) Another basic advantage of Chipmunk that I see is that it doesn't force you to use meters and kilograms. Box2D's performance and stability can suffer greatly if you use pixels, tiles, or some other more convenient arbitrary unit for distance. I've been moving away from having thresholds that need to be tuned in Chipmunk whenever possible. In Chipmunk 6, there are really only two left, one is size invariant the other can just be ignored 95% of the time anyway.

Chipmunk's performance is far better than Box2D, especially for projects that only want collision detection and don't heavily use physics (like 3-4x faster in that case). We also have a multi-threaded and NEON optimized solver available in Chipmunk Pro that makes things even faster.

Shameless plug: On top of the regular open-source part of Chipmunk, we also sell Chipmunk Pro where we've added a full Obj-C binding to make the API even simpler where possible, support Cocoa style memory management (including ARC support), and easier support for working with composite objects. It also has some platform specific optimizations (NEON and multithreaded solver), and our autogeometry module for doing deformable terrain or dynamic shape generation from images or procedural data at runtime.

Thanks, fixed in the develop branch.

Hum, what are the chances of this ever becoming open-source?

This sounds really interesting to me.

Now my post is useless, so please remove it too :)

removed spam :)

Lol for spam

cocos2d-x is cool but it definitely has some short-comings so this would definitely be great to try out at some point. When I first started with objective-c it felt weird after using c++ for so long but now I really dislike going back to c++ after using objective-c on some projects.