Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>So after a week of waiting, Apple Developer Technical Support managed to help me sort my problem out. Here is their response:</p> <blockquote> <p>"I've looked over your code and found a few things you need to be concerned about, some of which may contribute to your problem. In your <code>ControllerSwitchAppDelegate.m</code> source, you are implementing "<code>didRotate</code>" method. It might be worth checking for device orientation notifications at the view controller level rather than at the UIApplication level. This will make your code much more simpler and encapsulated allowing each view controller that is shown to handle its own rotation logic. You are also using multiple view controllers at the same time, that being, both "view" properties are being added and remove when the device is rotated. This is not exactly the common approach in which to use the UIKit. The idea is to present one view controller (or its view property) at a time and not have a parent view controller swap in different sub-view controllers. Granted on the surface your approach seems doable, but in the long run, I recommend a different approach.</p> <p>We have a sample called "AlternateViews", which can be found at - <a href="http://developer.apple.com/iphone/library/samplecode/AlternateViews/index.html" rel="nofollow noreferrer">http://developer.apple.com/iphone/library/samplecode/AlternateViews/index.html</a></p> <p>In this sample, it pretty much does what you need. It provides an "alternate" view controller for a given device orientation. Is merely presents one view controller over another using "presentModalViewController" with a transition property called "modalTransitionStyle" which will give you a cross fade affect."</p> </blockquote> <p>What I ended up doing was using a super view controller that presented and dismissed view controllers. Rather than swapping view controllers and removing sub views using the AppDelegate.</p>
    singulars
    1. This table or related slice is empty.
    1. POView Controller being sent a message even though it has been deallocated
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USMichael Gaylord
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POView Controller being sent a message even though it has been deallocated
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThanks for posting this. Maybe it's just me, but this doesn't seem like a very helpful answer from Apple. There's a big difference between "your approach seems doable, but in the long run, I recommend a different approach" and "here's why messages are being sent to deallocated view controllers in 3.0". Did they give you any more specifics, or was that it?
      singulars
      1. PO
      1. USMark Smith
    2. COThat was pretty much the whole e-mail. I could have followed it up further but it did in the end solve my problem. I suspect that the reason it changed in 3.0 had something to do with performance improvements.
      singulars
      1. PO
      1. USMichael Gaylord
 

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