A fast, easy to use, free, and community supported 2D game engine
EasyDev
Member
Hey developers,
I have a very simple app, and I don't want touches event to be activated, so i thought that if i do nothing about event touches they'll not be receivable by the app, but that's false… When I tap the screen a lot of time, my app bugs a lot ! But I never told to my app to receive touch events… I'm confuse… How to resolve this problem ?
Thanks in advance :)
chrisco
Member
I'm actually not 100% sure if this just blocks touches or the accelerometer as well, but you can try this:
[[UIApplication sharedApplication] beginIgnoringInteractionEvents];And since I find it a little hard to believe you don't need any touches at all, you'll need this as well ;)
[[UIApplication sharedApplication] endIgnoringInteractionEvents];moved to "cocos2d support" from "cocos2d games"
EasyDev
Member
First, thanks for your help ! :)
[[UIApplication sharedApplication] beginIgnoringInteractionEvents]; => I tried it, but it regrettably change nothing…
I also tried this, but same result :
[[CCTouchDispatcher sharedDispatcher] addTargetedDelegate:self
priority:0
swallowsTouches:NO];And finally I tried to create those both actions who was supposed to do nothing at their call, but that did not either work :
- (BOOL)ccTouchBegan:(UITouch *)touch withEvent:(UIEvent *)event {
return YES;
}
- (void)ccTouchEnded:(UITouch *)touch withEvent:(UIEvent *)event {
}Any ideas ? Thanks for your help :)
If you are doing nothing in the touch event handlers, I'm not sure how you can can get a bug from touches. What do you mean by "it bugs a lot"?
The code you listed:
- (BOOL)ccTouchBegan:(UITouch *)touch withEvent:(UIEvent *)event {
return YES;
}
Says for this CCNode it is handling every touch, not sure that is what you wanted.
EasyDev
Member
Says for this CCNode it is handling every touch, not sure that is what you wanted.
I had to try if it could still bug if I do nothing in the touch event handlers.
But I have to say that I am really stupid (perhaps because of my lack of rest). Thanks, you got me to try the thing that I forgot to try : putting NO on the square of YES in the ccTouchBegan method !
And… Surprise ! It doesn't work… :(
What do you mean by "it bugs a lot"?
Well, my app is very simple : there is a character which can be moved with the accelerometer. When you tap the screen at the very begining of the game (i think in the init method), it begins bugging : my character moves everywhere on the .x axis without that I move the accelerometer.
Any ideas ? Thanks for your help !
chrisco
Member
It kind of sounds like the physical movement of tapping the screen is affecting the accelerometer. You should be filtering the accelerometer readings to "smooth" them out - not sure, but I think you'd need a low-pass filter for this. There's some discussion about it here: Low-pass filtering
I've never personally implemented it myself, so I can't help you much beyond hopefully pointing you in the right direction.
EasyDev
Member
Here it is :
- (void)accelerometer:(UIAccelerometer *)accelerometer didAccelerate:(UIAcceleration *)acceleration {
gravite.x = acceleration.x * kGraviteMultiplieur;
}And in a tick method who is called at each frame, there is that :
perso.position = CGPointMake(perso.position.x+gravite.x, perso.position.y);
Did I wrong ?
Thanks for your help :)
chrisco
Member
@EasyDev - Did you take a look at the link I posted. I realize now it's a bit hidden in the post:
It may not be what you're after, but it's worth a look at. Right now you're feeding raw accelerometer data into your player's position, so it seems to me that bumping/tapping the device rapidly could give you some very erratic values from the accelerometer, and therefore in the position value.
I believe the filtering will essentially average out your accelerometer data to weed out any values that are way off from your basic "tilt the device" values. I think it would also help in situations where the player is being moved around a lot, like in a moving car on a bumpy road for example.
Here's what I do in a game of mine: in my case, the player slides back and forth along the bottom of the screen. This makes use of the low-pass filter as well as a player jitter adjustment I added for when the sensitivity is set higher, and an accelerometer jitter factor too.
I have these defined:
float accelJitter = 0.01;
float playerJitter = 1.0;
const float kFilteringFactor = 0.1;
UIAccelerationValue rollingY;
//this would the tick method
-(void) update: (ccTime) dt {
[self setPosition:self.lastPosition];
}
- (void)accelerometer:(UIAccelerometer*)accelerometer didAccelerate:(UIAcceleration*)acceleration {
BOOL shouldMove = NO;
rollingY = ((acceleration.y * kFilteringFactor) + (rollingY * (1.0 - kFilteringFactor)));
float accelY = acceleration.y - rollingY;
float newX = self.position.x + (sensitivity *-accelY);
if (accelY < -accelJitter || accelY > accelJitter) shouldMove = YES;
if (shouldMove) {
if (newX < playerMaxLeft-playerWidth/2) {
newX = playerMaxLeft-playerWidth/2;
}
if (newX > playerMaxRight-playerWidth/2) {
newX = playerMaxRight-playerWidth/2;
}
if (((newX - self.position.x) > playerJitter) ||
((self.position.x - newX) > playerJitter)) {
[self setLastPosition:CGPointMake(newX, self.position.y)];
}
}
}
EasyDev
Member
Thanks to both for your help, but there is still errors occuring :
[self setPosition:self.lastPosition]; => Request for member 'lastPosition' in something not a structure or union
[self setLastPosition:CGPointMake(newX, self.position.y)]; => HelloWorld may not respond to '-setLastPosition:'
And I think I didn't explain well the problem : The problem is not that by tapping on the screen the character moves, because this is normal. The problem is that when we tap on the screen a lot of time and if then we stop tapping on the screen, the character will not move enough correctly, he will move from left to right no matter how ! I hope you understood.
Thanks for your help :)
EasyDev
Member
So wait, you want to move the character by tapping but you want to turn touches off? I'm thoroughly confused.
No no, i just said that it is normal that by tapping on the screen the character moves because tapping on the screen moves the accelerometer. The problem is that when we tap on the screen a lot of time and if then we stop tapping on the screen, the character will not move enough correctly, he will move from left to right no matter how ! I hope you understood.
@sabshire Your code malherously doesn't work.
That code does indeed work, as I am using it right now. In your example, you would my "lastPosition" to your "gravite".
One question I have is this... Why would you tap on the screen if the character moves by the accelerometer? There's nothing wrong with doing that, but I am throughly confused as to why you would tap the screen a lot to move a character with the accelerometer.
EasyDev
Member
People could tap on the screen by curiosity, and do bug the application. But the question is not to know why people will tap the screen but it's to know how to do not bug the app by tapping on the screen. Cocos2d is very powerful by some angles, but by other ones like this one, cocos2d's really crap…
Thanks for your help, I really appreciate :)
chrisco
Member
People tapping on the phone has absolutely nothing to do with Cocos2D. I could throw my phone in the toilet and have my game crash - that doesn't make Cocos2d "crap" because it doesn't automatically handle that situation. Although I guess it would make my phone crap, but that's not the point.
The point is, you need to filter the readings that are given to you by the accelerometer, as has been mentioned multiple times. Sabshire posted some very helpful code, and you complained that it didn't work - it will work if you take the time to understand it and incorporate it into your game. There's no -ignorePeopleTappingOnThePhoneWhenIWouldPreferThatTheyTiltIt method that's going to solve your problem.
There's one main question you need to answer and that is "Is the likelihood of people constantly tapping the screen greater than the amount of time it's going to take me to figure out how to solve this problem?". If it's yes, then take the time to read up on accelerometer data and do not blame the engine that does almost everything else for you.
chrisco
Member
Fair enough - I was having a rough day when I read your response, and it rubbed me the wrong way, so I apologize if I came off overly harsh.
In regards to @Sabshire's code, I'm sure that it doesn't work for you in its present state since it was built specifically for his game. But if you read through it carefully and try to understand what it's doing, line for line, then you can take those concepts and apply it to your own code. I'm sure @Sabshire would help out in explaining it if you had specific questions.
Oh and I'm sure your English is better than my <fill in any language here> :P
EasyDev
Member
Don't worry, you wasn't too rude, but i'm a bit impatient, so that's good to have some more rude answers sometimes. Furthermore, you don't have to be made because I understood one word on two, haha.
<fill in any language here>
I'm french ;P
Okey, so let's get in back. I tried to understand this code to do my character move from left to right & from right to left, and there is my problems : How I am supposed to declare sensitivity ? May I replace self by my character : "perso" ?
chrisco
Member
Ah, oui ;)
So, yeah, I'm guessing self could be replaced by perso in your case. I think @Sabshire may have had his accelerometer code within his sprite's class, but yours looks as though it may be in the sprite's (perso's) parent layer.
I do see what you mean regarding sensitivity, though - there's no real reference for what that value may be in the code sample. I'm guessing he's pulling the value from a slider that the player adjusts themselves - if that's the only thing holding you back right now, try defining it as 1.0 for now and see if that helps (that should indicate that the sensitivity has no effect).
EasyDev
Member
I got this code to work ! Very great, no more lags ! Merci beaucoup ;) ! But I have one last question : Is it possible to do something when the user clicks on the homeButton ? I know that - (void)applicationWillResignActive:(UIApplication *)application { can do this but it will also run the code when the user receive a call, so that's not what I want.
Any ideas ?
You must log in to post.