Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The method <code>viewWillAppear</code> should be taken in the context of what is going on in your own application, and not in the context of your application being placed in the foreground when you switch back to it from another app.</p> <p>In other words, if someone looks at another application or takes a phone call, then switches back to your app which was earlier on backgrounded, your UIViewController which was already visible when you left your app 'doesn't care' so to speak -- as far as it is concerned, it's never disappeared and it's still visible -- and so <code>viewWillAppear</code> isn't called.</p> <p>I recommend against calling the <code>viewWillAppear</code> yourself -- it has a specific meaning which you shouldn't subvert! A refactoring you can do to achieve the same effect might be as follows:</p> <pre><code>- (void)viewWillAppear:(BOOL)animated { [super viewWillAppear:animated]; [self doMyLayoutStuff:self]; } - (void)doMyLayoutStuff:(id)sender { // stuff } </code></pre> <p>Then also you trigger <code>doMyLayoutStuff</code> from the appropriate notification:</p> <pre><code>[[NSNotificationCenter defaultCenter] addObserver:self selector:@selector(doMyLayoutStuff:) name:UIApplicationDidChangeStatusBarFrameNotification object:self]; </code></pre> <p>There's no out of the box way to tell which is the 'current' UIViewController by the way. But you can find ways around that, e.g. there are delegate methods of UINavigationController for finding out when a UIViewController is presented therein. You could use such a thing to track the latest UIViewController which has been presented.</p> <p><strong>Update</strong></p> <p>If you layout out UIs with the appropriate autoresizing masks on the various bits, sometimes you don't even need to deal with the 'manual' laying out of your UI - it just gets dealt with...</p>
    singulars
    1. This table or related slice is empty.
    1. POWhy does viewWillAppear not get called when an app comes back from the background?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USocculus
    1. USocculus
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POWhy does viewWillAppear not get called when an app comes back from the background?
      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. VTUpMod
    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. VTAcceptedByOriginator
    1. COThanks for this solution. I actually add the observer for UIApplicationDidBecomeActiveNotification and it works very good.
      singulars
      1. PO
      1. USWayne Liu
    2. COThis is certainly the correct answer. Of note, however, in response to "there's no out of the box way to tell which is the 'current' UIViewController", I believe that `self.navigationController.topViewController`effectively provides it, or at least the one on the top of the stack, which would be the current one if this code is is firing on the main thread in a view contoller. (Could be wrong, haven't played with it a lot, but seems to work.)
      singulars
      1. PO
      1. USMatthew Frederick
    3. CO`appDelegate.rootViewController` will work too, but it might return a `UINavigationController`, and then you'll need `.topViewController` as @MatthewFrederick says.
      singulars
      1. PO
      1. USsamson
 

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