Dude, I ran into the same problem.. and here is what I found about using parentViewController:
Note that as of 5.0 this no longer
will return the presenting view
controller.
This was written in the header file of UIViewController…
I am using ShareKit, and the modalViewController was working perfectly in iOS4, but in iOS5, it just won’t dismiss itself! This is because in their code, they are using:
[[currentView parentViewController] dismissModalViewControllerAnimated:animated];
and parentViewController will return nil, since this is a modal presented view controller…
By searching for a solution, I found your question.. So, I decided to fix it myself 😛
I changed the previous line to this:
[currentView dismissModalViewControllerAnimated:YES];
Works like a charm.
EDIT: Depending on how you interpret the original question, there are two answers. Here’s the second:
In iOS5 it seems that the modal controller only dismisses itself when you click the curl, but not above the curl or the backgound. In iOS5, in order to actually get the modal view to dismiss itself when tapping the background or above the curl I added the following code to the controller, to listen to taps on the modal view, but ignore taps to buttons. This should mimic the behavior in previous version of iOS when working with a modal controller with page curl.
- (void)viewDidLoad
{
UITapGestureRecognizer *tap = [[UITapGestureRecognizer alloc] initWithTarget:self action:@selector(handleTap:)];
tap.numberOfTapsRequired = 1;
tap.numberOfTouchesRequired = 1;
tap.delegate = self;
[backgroundView addGestureRecognizer:tap];
}
- (BOOL)gestureRecognizer:(UIGestureRecognizer *)gestureRecognizer shouldReceiveTouch:(UITouch *)touch{
//change it to your condition
if ([touch.view isKindOfClass:[UIButton class]]) {
return NO;
}
return YES;
}
- (void)handleTap:(UITapGestureRecognizer *)sender {
[self dismissModalViewControllerAnimated:YES];
}