IPhone UIToolBar UiBarButtonItem Transition problem?

I'd say it depends on when you create the UIToolbar and its back button, and when you add them to the new view.

I'd say it depends on when you create the UIToolbar and its back button, and when you add them to the new view. Also -- is there a particular reason why the viewWillAppear and viewWillDisappear lines need to be part of the animation? I'd experiment with pulling them out of the animation, and also moving the viewDidDisappear and viewDidAppear into a callback function invoked when the animation completes; see docs for UIView setAnimationDidStopSelector.

Not sure if that will help, but it might.

Thanks Amagrammer I moved viewWillAppear and viewWillDisappear out of animation block and now work good :) Thank you! – user140902 Jul 21 '09 at 5:16 You are very welcome! You are the first person I've really been able to help on Stack Overflow.

– Amagrammer Jul 21 '09 at 21:37.

The way the cached transitions work is the iPhone takes a snapshot of the window and does some transforms on it as if it were an image. The uncached transitions actually redraw the live window as it is transformed. Your problem seems to be that the back button isn't present in the view when the snapshot is taken.

The solution may be to add the button manually rather than relying on the navigation view controller or something.

It could be a problem with a difference between the two views. Have a look at both your views' attributes in the IB; did you specify a status bar for both? Or just one of them?

This could cause a difference in vertical offset and can cause some problems I think. You can perhaps solve this small problem by setting your two frames equal BEFORE the animation transition code: newViewController.view. Frame = self.view.

Frame; (This should also then allow you to revert back to cache:YES) On another matter, you may want to consider adding the subview onto the current window instead of the current window's current view, thus: self. View superview addSubview:newViewController. View; This way you can remove the explicit calls to all the window events.

You will also need to link the transition to your window instead of the current view otherwise animation will not work: UIView setAnimationTransition:transition forView:self.view. Superview cache:YES; I was struggling with similar problems, and eventually got this right. You may also want to try using QuartzCore foundation animations: #import // ... // get the view that's currently showing UIView *currentView = self.

View; currentView retain; // get the the underlying UIWindow, or the view containing the current view UIView *theWindow = currentView superview; UIView *newView = myNewViewController. View; newView. Frame = currentView.

Frame; // add subview theWindow addSubview:newView; // set up an animation for the transition between the views CATransition *animation = CATransition animation; animation setDuration:0.8; animation setType:kCATransitionPush; animation setSubtype:kCATransitionFromRight; animation setTimingFunction:CAMediaTimingFunction functionWithName:kCAMediaTimingFunctionEaseInEaseOut; theWindow layer addAnimation:animation forKey:@"SwitchToView1"; And to transition back, do the same (except in opposite direction of course) replacing your add subview with: self. View removeFromSuperview; With this the previous window will come to the foreground again, but its events will not be triggered (I'm still not sure why). I hope this sorts things out for you and helps a lot of other people.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.