cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   bsharp42
   Member

   Lets say I have 40 sprites on the screen, and I want to be able to move them via touches.

   Right now, I'm just doing something like

   when ccTouchBegan
   {
   for each sprite
   {
   if (sprite location == ccTouchBegan location)
   {
   do evil stuffz
   }
   }
   }

   and for the sprite location == ccTouchBegan location,
   I simply do something like

   if ( sprite.location.x < (touch.location.x+radius) && sprite.lcation.x > (touch.location.x-radius) && sprite.location.y < (touch.locaiton.y+radius) && sprite.location.y > (touch.location.y-radius) )

   which I feel like is a ghetto, inefficient way of doing it.....

   So I guess what I'm asking is, does what I'm doing above sound a decent way to do it ?? Is there a better way ?

   Posted 2 years ago #
2. 

   Nicke
   Member

   http://juanmunozar.blogspot.com/2009/02/cocos2d-iphone-dynamically-touch.html

   Posted 2 years ago #
3. 

   cjl
   Member

   I think the new touch dispatcher can do what you need.

   Check of 'TouchesTest' included with the cocos2d source code.

   Posted 2 years ago #
4. 

   Osiris
   Member

   Im sure this is another dumb question and I do always hunt for a while before asking...

   I understand how to start a touch and I understand how to use ccTouchMoved: to pick up the movement and have a sprite follow your touch. I've been doing this for my game.

   Some people have suggested that it might be easier with just left<->right movement button instead of a slide bar.

   How do I get it to detect that the button is being HELD DOWN? rather than just touched. Right now, if I hold the button, it only registers more than one touch if I wiggle my finger around.

   Thanks in advance

   Posted 2 years ago #
5. 

   cjl
   Member

   Osiris, for one way of doing it with menu items, see:

   http://www.cocos2d-iphone.org/forum/topic/66#post-278

   Posted 2 years ago #
6. 

   adunsmoor
   Member

   Osiris,

   You can get the effect you describe by using touches and the scheduler together. In other words, set a flag when touches begin and unset it when touches end or are canceled. Then use a separate method that is called by the scheduler to check the status of the flag and update the game based on the button being pressed or not.

   Something like:
   
// called by ccTouches* begin or moved
- (void) handleTouch ... {
...
lastTouchLocation = CGPointMake(touch.position);
touchDown = YES;
}
// called by ccTouches* end or canceled
- (BOOL) handleTochesEnded ... {
lastTouchLocation = CGPointMake(0.0, 0.0);
touchDown = NO;
}
// called by registering with layer's scheduler
- (void) tick:(float)delta {
if (touchDown) {
// use lastTouchLocation to do something
}
}


   Posted 2 years ago #
7. 

   Osiris
   Member

   @adunsmoor - thanks - that what I ended up doing. Works like a charm. Its just when you don't know the system very well, you keep running into both things you didnt know it included and things you think "It should be in here somwhere" and its not...

   Would love big thick technical manuals like Microsoft USED to publish with Excel... where they step you through every nuance of every function with examples for almost every function.

   LONG LIVE TURBO PASCAL!

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.