Hey guys

Update version 1.5

-OSX 4 bug fix.
-Switch to EXTREME mode.
- Faster gameplay.
- Improved Graphics
- A lot more meteors :)
-Game tunning.

version 1.5 updated on LITE version and FULL version.
Enjoy :)

website: http://www.lbinteractive.com/ispaceport/
twitter: https://twitter.com/LBInteractive
youtube: http://www.youtube.com/user/iSpacePort
iTunes: http://itunes.apple.com/WebObjects/MZStore.woa/wa/viewSoftware?id=327905105&mt=8

Hi Alonstudio,
I need your help in drawing multiple lines using cocos2d. Right now i m able to draw only single line on touches moved. But when i draw another line, the 1st line gets deleted. I am sharing my code with you. Can you please help me on this?

Please go through the following code and let me know if am I doing any thing wrong or is there any other way of doing this?

I am collecting the CGPoints on touchesMoved and storing them in a mutable array and later in touchesEnd i am adding that array as object to another mutable array.

-(void) ccTouchesMoved:(NSSet *)touches withEvent:(UIEvent *)event
{
UITouch *myTouch = [touches anyObject];
CGPoint location = [myTouch locationInView:[myTouch view]];

lastLocation = [ myTouch previousLocationInView: [myTouch view]];

CGPoint point = [[CCDirector sharedDirector] convertToGL:location];

newPoint = point;

NSString *coordPt = [NSString stringWithFormat:@"%@", NSStringFromCGPoint(point)];

[persistance_obj->cgPointArray addObject:coordPt];
}

-(void) ccTouchesEnded:(NSSet *)touches withEvent:(UIEvent *)event
{
[self addChild:[drawLine node]];

NSMutableArray * tempArray = [[NSMutableArray alloc]init];
tempArray = [persistance_obj->cgPointArray copy];

[drawPath addObject:tempArray];
[tempArray release];

[persistance_obj->cgPointArray removeAllObjects];
}

This is the code where I am actully drawing a line. This method i have written in a class which is a child class of CCNode.

-(void)draw
{
glEnable(GL_LINE_SMOOTH);
glLineWidth(2.0f);
glColor4f(1.0f, 0.0f, 0.0f, 1.0f);

int x;

if(indexVal > 0)
{
x = indexVal - 1;
}
else
{
x = indexVal;
}

NSArray *array = [drawPath objectAtIndex:x];
for(int i = 0; i < [array count]; i++)
{
startLocation = CGPointFromString([array objectAtIndex:i]) ;
if(i+1 < [array count])
{
endPoint = CGPointFromString([array objectAtIndex:i+1]);
}
else
{
endPoint = CGPointFromString([array objectAtIndex:i]);
}
ccDrawLine(startLocation, endPoint);
}
}

You could accomplish the same thing with a "one-shot" schedule method also:

- (void)init { [self scheduleNextSprite]; }

- (void)scheduleNextSprite {
    [self scheduleSelector:@selector(scheduleNextSprite) forTarget:self delay:gDeploymentInterval];
    [self launchSprite];
}

Might not be the most performant way of doing it but it's fairly simple. Oh nice, looks like it's on it's way: http://code.google.com/p/cocos2d-iphone/issues/detail?id=630

Interesting addition that would be great for some things, but I also like having the control in the scene rather than a static scheduler as described above...I can add more control to change the update time dynamically for launching sprites more frequently as the pace picks up, like placing chips on the belt for eFactory shown in this post.

Here's an example of a timer set in the scheduler called each tick with [self updateBelt:dt]:

- (void) updateBelt:(ccTime)dt
{
	timeSinceLastLaunch += dt;   //timeSinceLastLaunch is a global variable

	if (timeSinceLastLaunch > gDeploymentInterval)  //while gDeploymentInterval can be a constant or variable
	{
		[self launchSprite];
		timeSinceLastLaunch = 0;
	}
}

During game play, I can speed up the action by decrementing the comparison variable, which above is gDeploymentInterval.

Hope this helps.

Largemouth

Not sure if this made it into cocos2d. You can add this method as a category:

@interface CCScheduler (ScheduleSelector)
- (void)scheduleSelector:(SEL)selector forTarget:(id)target delay:(ccTime)delay;
@end

@implementation CCScheduler (ScheduleSelector)
- (void)scheduleSelector:(SEL)selector forTarget:(id)target delay:(ccTime)delay {
	[[CCActionManager sharedManager] addAction:[CCSequence actions:
					[CCDelayTime actionWithDuration:delay],
					[CCCallFunc actionWithTarget:target selector:selector],nil]
				target:target paused:NO];
}
@end

Word! Had been coding along happily for a while, then decided I wanted a phys engine after all (as you do). Added the sources, compiled and whack, 2263 errors.

Adding the header search path did the trick. Legend!

I now have this working with a Singleton and have tested on both 3.2 and 4.1 in the simulator. Happy to share the code if anyone else is new to this and struggling, just PM me. :)

Hello.

I've decided to go the Singleton route and start this again, because using the code above was causing OS4 to crash (although it works fine on 3.2 iPad). I guessed it had something to do with Multitasking, I have the other methods in and tried saving when they were called but sadly, still crashes.

I'll try again, but it's an excuse to learn about Singletons anyway :)

Thanks for posting.

@mrTortex - There's a few more functions similar to "applicationWillTerminate" that you need to implement, the recent cocos2d templates actually post the stubs for you so it's worth checking out.

Does this work happily with multitasking in OS4? I have no OS4 device to test with yet, and it appears to not work on the simulator. It works perfectly with OS3.2 on the iPad though. The reason I ask is a few people have told me this is not the way to save data.

Thanks for responding, it's working now. Saving and loading is fun :)

Hi,

Something like this:

#import YourAppDelegate.h

// ... 

	YourAppDelegate *appDel = [[UIApplication sharedApplication] delegate];
	appDel.gLevel += 1;

HTH
-Mark

Sorry for returning to this. I'm creating the properties in the app delegate (gLevel and gScore). I want to do a simple test where a button adds +1 to the int, and then I can test saving. However, how do I gain access to the properties which are in the app delegate?

Are you updating an integer or updating a label?

You can update a CCLabel by:

[label setString:[NSString stringWithFormat:@"%d", yourInteger]];

hello

i have done what you wrote and i cant count anything to my integem
how do i count stuff to it

i tried
myint = myint + myotherint;

but it does not work
the label is still 1;

how we set the anchor point for a body that has a composite shapes? For example, a circle with a triangle base?

Thanks :)

Have re-uploaded the code if anyone is interested.
Sorry @Bongeh wasn't paying attention to the list!

http://files.me.com/shivaz/5jb01u

Justin

could you reupload the sample code please?

you can always open an issue:

http://code.google.com/p/cocos2d-iphone/issues/list

riq follows that list pretty closely.

Hm ... i still would prefer crmagicxxx idea.

Why not include this method?

-(void) schedule: (SEL) selector interval:(ccTime)interval repeat:(BOOL) yesNo;

Theres always option 1 crmagicxxx mentions. Personally I prefer that to the delay and callfunc method.

Is there a schedule once function in the meantime?

This is something i miss quite often and I agree that Delay & CallFunc feels "dirty".

Just wanted to check before I take the plunge on setting this up...

Will Clang still work with the objective-c code in .mm files, and just not the c++?

I'm still running OSX 10.5 & xcode 3.1.4, so would need to set it up manually. Don't really want to upgrade to 10.6 until I've got this box2d based project out the door, unless it makes this step much easier?

Submitted a couple of patches and issue #613 for this. It will be solved (milestone is currently set to 0.8.3).

Hi guys, I am new bee and I was wondering the code listed on cool projects for air hockey game.cpMouse was used there, Does anybody now what code should use the same function for the new cocos2d 0.8.1 version.Thanks

Really? I'll go back and check, but I'm fairly certain I got warnings about possible leaks for every singleton in Cocos2D.

It doesn't report Singletons as memory leaks, for example it is quite happy with Director. It doesn't like the style of coding used in SimpleAudioEngine because the set up is spread across alloc and init and the static analyzer can not cross function boundaries.

The static analyzer is nice but it is worthwhile getting familiar with the (pretty major) limitations. Once it is working as Apple intend it will be awesome but it will still be impossible to detect all problems through static analysis.

They're not false positives per se, but they're not something to worry about either. It reports singletons as memory leaks, which technically they are, but it doesn't matter because you don't really need to ever deallocate a singleton anyway.

The static analyzer is included in Xcode 3.2:

http://developer.apple.com/mac/library/featuredarticles/StaticAnalysis/index.html

It is really nice. I guess the errors/warnings it finds in cocos2D are false positives?