Databases
StackOverflow2013
Postsdbo
POIPhone - After dismissing Modal View Controller - gap is left at top of page
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POIPhone - After dismissing Modal View Controller - gap is left at top of page
    primarykey
    data
    text
    <p>When starting the app, if the user doesn't have login information stored, I want to display a modal view controller to force the entry of this information. I found through trial and error, that this had to occur in viewDidAppear of my root view controller. I tried to put it in viewDidLoad and viewWillAppear, but those didn't work unless I assigned the view of the root view controller to the view of the navigation controller used in the modal which then caused other issues...</p> <p>So I have:</p> <pre><code>- (void)viewDidAppear:(BOOL)animated { NewAccountViewController *newAccountViewController = [[[NewAccountViewController alloc] initWithNibName:@"NewAccountViewController" bundle:nil] autorelease]; UINavigationController *accountNavigationController = [[UINavigationController alloc] initWithRootViewController:newAccountViewController]; [self presentModalViewController:accountNavigationController animated:YES]; } </code></pre> <p>And in the newAccountViewController I have a simple navigation item button that dismisses the modal view controller with dismissModalViewController.</p> <p>This all works and when the modal is dismissed a view in a navigation controller is visible with its navigation item title at the top....</p> <p>But there is a white gap about the same size as the status bar between the status bar and the top of the blue navigation item bar. If I don't do the modal, then the gap is never there. It only occurs after the modal is presented and dismissed. I've tried doing animated:NO on both the present and dismissModalViewController. I've also tried not using the navigation controller in the modal, and that did nothing as well. Any ideas would be great! Thanks.</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USBrian
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POIPhone - After dismissing Modal View Controller - gap is left at top of page
      1. USennuikiller
      1. VTFavorite
    2. VO
      singulars
      1. POIPhone - After dismissing Modal View Controller - gap is left at top of page
      1. USLoganFrederick
      1. VTFavorite
    3. VO
      singulars
      1. POIPhone - After dismissing Modal View Controller - gap is left at top of page
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI haven't tested this hypothesis, but it may be the case that setting or not setting the window as key is related to this. You should always set it as the key window using [UIWindow makeKeyAndVisible] in your app delegate's applicationDidFinishLaunching: method. If you forget to do that, some subtle behavior changes might occur, possibly including this status bar thing.
      singulars
      1. POIPhone - After dismissing Modal View Controller - gap is left at top of page
      1. USTyler
 

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