Databases
StackOverflow2013
Postsdbo
POMultiple Presented View Controllers and Rotation on iPad
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POMultiple Presented View Controllers and Rotation on iPad
    primarykey
    data
    text
    <p>I have recently run into an issue when porting some code from an iPhone app over to the iPad. It may be related to the issue described <a href="https://stackoverflow.com/questions/8891789/modal-view-controller-dont-rotate-correctly">here</a>, though I found the explanations/solutions of that question unsatisfactory. The scenario is this:</p> <ol> <li><p>View controller 'A' (The Root View Controller) presents a modal view controller (call it 'B') with the "Form Sheet" modal presentation style.</p></li> <li><p>View controller B presents view controller 'C' with the "Full Screen" modal presentation style.</p></li> <li><p>The iPad is rotated while view controller C is the top-most presented view controller.</p></li> <li><p>Upon dismissal of C, B is re-displayed, but has the incorrect orientation.</p></li> </ol> <p>As far as I can tell, there should not be an issue with chaining of multiple presented view controllers -- in fact, this behavior is explicitly supported in the <a href="http://developer.apple.com/library/ios/#featuredarticles/ViewControllerPGforiPhoneOS/ModalViewControllers/ModalViewControllers.html#//apple_ref/doc/uid/TP40007457-CH111-SW1" rel="nofollow noreferrer">Presenting View Controllers from Other View Controllers</a> documentation. I have also read the following statement in the <a href="http://developer.apple.com/library/ios/#releasenotes/General/RN-iOSSDK-5_0/_index.html" rel="nofollow noreferrer">iOS 5 Release Notes</a>:</p> <blockquote> <p>Rotation callbacks in iOS 5 are not applied to view controllers that are presented over a full screen. What this means is that if your code presents a view controller over another view controller, and then the user subsequently rotates the device to a different orientation, upon dismissal, the underlying controller (i.e. presenting controller) will not receive any rotation callbacks. Note however that the presenting controller will receive a viewWillLayoutSubviews call when it is redisplayed, and the interfaceOrientation property can be queried from this method and used to lay out the controller correctly.</p> </blockquote> <p>As far as I can tell, this does not occur -- View controller B receives a call to -shouldAutoRotateToInterfaceOrientation but the value the interfaceOrientation parameter in this call is the value of view controller B's interface orientation when it presented view controller C, not the value of C's interface orientation upon dismissal. Since we're on an iPad, all these view controllers return YES in -shouldAutoRotateToInterfaceOrientation. Thus the bounds of B's view never change, so -willLayoutSubviews is never called.</p> <p>I have tried saving the orientation of view controller C in a callback to B before B dismisses it, and then using that information the next time -shouldAutoRotateToInterfaceOrientation is called and returning YES only for the orientation of C when it is dismissed. This fixes, the broken UI that appears without making this check, but view controller B does not update its interface orientation to this value, so subsequent modal presentations will animate in/out from the wrong side of the device. </p> <p>Has anyone been able to successfully get a view controller configuration like this working? It doesn't seem like that unusual of a scenario, so I am a little surprised that it isn't working as I initially expected it to.</p> <p>Thanks in advance.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USjamie
    plurals
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POMultiple Presented View Controllers and Rotation on iPad
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POMultiple Presented View Controllers and Rotation on iPad
      1. USC4 - Travis
      1. VTFavorite
    3. VO
      singulars
      1. POMultiple Presented View Controllers and Rotation on iPad
      1. This table or related slice is empty.
      1. VTUpMod
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload