User input as events « cocos2d for iPhone

User input as events

(4 posts) (3 voices)

Tags:

No tags yet.

JamesK
Member

I'm a little confused as to how you handle user input via events given that some input may have a time element.

For example, in a shooter you may tap the screen to fire and hold the touch to continually fire, in this case the refire rate would be based on the time between shots whereas in the touch event you have no concept of the delta.

Is it a case that you set input flags that an update method can then process? Or do you store the time in your touch events and calculate it there?

As an aside, do the touch events run on the same thread as the main update method? as I guess this would effect whether you have to sync access to items both might access.

Posted 1 year ago #
pabloruiz55
Member
I do it like you mention:

on touch began: i set isFiring = YES;
on touch ended: i set isFiring = NO;
then on my scheduled update method i check:
```
//IN my update method

if(isFiring && timePassedSinceLastShot >= fireInterval)
{
  //SHOOT!
  timePassedSinceLastShot =0;
}
timePassedSinceLastShot ++
```
Posted 1 year ago #
Karl
Member
Another way to do it:

touch began:
```
[self fireGuns];
[self schedule:@selector(fireGuns) interval:kAutoFireShotInterval];
```
touch ended:
```
[self unschedule:@selector(fireGuns)];
```
Everything happens on the same thread unless you intentionally make a different thread via NSThread or NSOperationQueue.
Posted 1 year ago #
JamesK
Member

Thanks for the replies, that clears things up for me.

Posted 1 year ago #

You must log in to post.