Threads and animations

[tosibamaniac]

I want to pause the main thread NSThread while I animate, is there any way to do create an animation in a another thread. Also I INSIST on using this, so plese don't say me to use delegates, because that is NOT posible in this case!

[smithdale87]

You should never pause the main thread. EVER. I INSIST.

[creyon]

You should find a way to 'pause' the UI in your application while your animation takes place. Pausing the main thread is not an option.

[tosibamaniac]

Originally Posted by creyon

You should find a way to 'pause' the UI in your application while your animation takes place. Pausing the main thread is not an option.

Ok, but here I have an problem:

-(BOOL)yesOrNo {
// I need to animate and wait for an animation
return YESorNO;
}

[dany_dev]

you should animate in this mode Creating Basic Animations on iPhone | Switch on the Code

[tosibamaniac]

Originally Posted by dany_dev

you should animate in this mode Creating Basic Animations on iPhone | Switch on the Code

I know, but I musn't return before I finish the animation.

Bump

[nobre84]

You can do it, but its an ugly hack. Its always best to make your UI assinchronous. This can be accomplished by doing whatever you need to do on the didStopSelector instead, and not wasting cycles waiting.
Anyway, try this ...

-(BOOL)returnYesOrNo {
waiting = YES;        // declared as ivar

[UIView beginAnimations:nil context:NULL];
[UIView setAnimationDidStopSelector:@selector(stopWaiting)];
[UIView setAnimationDelegate:self];
//stuff to animate
[UIView commitAnimations];

NSRunLoop *theRL = [NSRunLoop currentRunLoop];
while (waiting && [theRL runMode:NSDefaultRunLoopMode beforeDate:[NSDate distantFuture]]);
return YESorNO;
}
-(void)stopWaiting {
waiting = NO;
}

[creyon]

You can:
- Pause your UI before the animation starts
- start the animation but set a didStopSelector delegate like this:

	[UIView beginAnimations:nil context:nil];
	[UIView setAnimationDuration:0.3f];
	[UIView setAnimationDelegate:self];
	[UIView setAnimationDidStopSelector:@selector(animationFinished:finished:context:)];
	
//stuff
	[UIView commitAnimations];

- when the animation finishes your code will call:

- (void) animationFinished:(NSString *)animationID finished:(NSNumber *)finished context:(void *)context {}

there you can unpause your UI and continue with your app's normal flow.

[dany_dev]

there aren't motive to don't use

[UIView setAnimationDidStopSelector:@selector(yourAnimationHasFinished:finished:context:)];

and then inrecept the ending with

- (void)yourAnimationHasFinished:(NSString *)animationID finished:(BOOL)finished context:(void *)context;

if you like, you can create another thread, where there is a where(!myBool){ sleep(0.2);} myBool is setted to NO; and set it to YES only when animation is finished using callback, but i don't see the motive to don't just use on you main thread.