A fast, easy to use, free, and community supported 2D game engine
I am having a strange issue where as i move from one level to the next (scene) once one has been accelerometer enables, all the ones following can't be. I need in all, and if i disable in level 1, level two is and thats it, and so on.
any ideas?
self.isAccelerometerEnabled = YES;
thats what i use
Sorry i didn't really understand your problem.
You should set self.isAccelerometerEnabled = YES; for each layer you want to receive accelerometter events.
I think that by default it is off.
i do. and i do it for each scene. each new file, a .h and .mm, is a scene, and i change scenes between each level like so:
[[CCDirector sharedDirector] replaceScene:[CCCrossFadeTransition transitionWithDuration:0.5 scene:[Space3Scene scene]]];
to move to the next level.
I have the self.isAccelerometerEnabled = YES; on each one in the init but it does not seem to work past the first level that uses it
notice you have to set that in your layers not in your scenes, are you doing that?
Also are you implementing the method for receiven the accelerometter events and setting the update interval in each one?
this is where i put the self.isAcc... you know :)
-(id) init
{
if( (self=[super initWithColor:ccc4(0,0,0,0)] )) {
[FlurryAPI logEvent:@"Space Demo Started"];
CGSize winSize = [[CCDirector sharedDirector] winSize];
self.isTouchEnabled = YES;
ballsLeft = 10;
MenuExist = FALSE;
blockerBall = 1;
blockerExist = FALSE;
/*
CCSprite * bg = [CCSprite spriteWithFile:@"Blackblue.png"];
bg.position = ccp(160, 240);
[self addChild:bg z:-1];
*/
// enable accelerometer
self.isAccelerometerEnabled = YES;like that, and then it continues
- (void)accelerometer:(UIAccelerometer *)accelerometer didAccelerate:(UIAcceleration *)acceleration {
//do stuff in here
}and then that is how i use the accelerometer. do i have to call an update on it like this kind of thing?
[self schedule:@selector(tick:)];So I found a temporary solution for now, which is still scary that it is needed.
- (void)ContinueButtonTapped:(id)sender {
self.isAccelerometerEnabled = NO;
[[CCDirector sharedDirector] replaceScene:[CCCrossFadeTransition transitionWithDuration:0.5 scene:[Space3Scene scene]]];
}as you can see I added self.isAccelerometerEnabled = NO; to my code anytime I was about to move from one scene to layer that had it enabled to another. when i move to the main menu or game over scene i don't need that because by default it is off so is getting the self.isAccelerometerEnabled = NO; when that loads. This is very strange that this happened out of no where but at least I can continue on for now.
If you figure it out please let me know, if not at least I have it working again. :)
enmeii
Member
I know the reason.
There are 2 screens. One is old and going to disappear, another is new and going to be shown.
The new one enter, the method is called first.
-(void) onEnter
{
// register 'parent' nodes first
// since events are propagated in reverse order
if (isTouchEnabled)
[self registerWithTouchDispatcher];
// then iterate over all the children
[super onEnter];
if( isAccelerometerEnabled )
[[UIAccelerometer sharedAccelerometer] setDelegate:self];
}Then the old screen is called OnExit second.
-(void) onExit
{
if( isTouchEnabled )
[[CCTouchDispatcher sharedDispatcher] removeDelegate:self];
if( isAccelerometerEnabled )
[[UIAccelerometer sharedAccelerometer] setDelegate:nil];
[super onExit];
}So the onExit method clears the UIAccelerometer.
But I don't know how to figure it out.
I have the same problem.
enmeii
Member
Ok, I found the solution. I hope it's right.
Change your onExit method as below in CCLayer.m.
Check if the Delegate of UIAccelerometer is self first. If it isn't, leave it alone. Otherwise, set the delegate to nil as original code.
-(void) onExit
{
if( isTouchEnabled )
[[CCTouchDispatcher sharedDispatcher] removeDelegate:self];
if( isAccelerometerEnabled )
//[[UIAccelerometer sharedAccelerometer] setDelegate:nil];
if ([[UIAccelerometer sharedAccelerometer] delegate] == self) {
[[UIAccelerometer sharedAccelerometer] setDelegate:nil];
}
[super onExit];
}
Mark Sawicki
Member
Hi,
just wanted to say that the order of execution changes if you are using a transition between scenes or not..
i.e. if you are going to SceneTwo from SceneOne:
**Without a transition
--SceneTwo init called
-SceneOne onExit called
-SceneOne dealloc called
--SceneTwo onEnter called
--SceneTwo onEnterTransitionDidFinish called
**With a transition
--SceneTwo init called
--SceneTwo onEnter called
-SceneOne onExit called
--SceneTwo onEnterTransitionDidFinish called
-SceneOne dealloc calledSo, as far as I know, if you are using a transition between scenes, you should be using onEnterTransitionDidFinish of the new scene for stuff you are waiting to be completed from onExit of the previous scene.
-Mark
You must log in to post.