Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>They are not in any of your view controllers because iOS adopts a 'delegate' design pattern, where you can be assured that a method will fire upon a class (in this case, the App Delegate for your application) when required.</p> <p>As a learning process, why don't you just put NSLog's in those methods to see when they're fired?</p> <pre><code>- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions { // Override point for customization after application launch. NSLog(@"didFinishLaunchingWithOptions"); [self.window makeKeyAndVisible]; return YES; } - (void)applicationWillResignActive:(UIApplication *)application { /* Sent when the application is about to move from active to inactive state. This can occur for certain types of temporary interruptions (such as an incoming phone call or SMS message) or when the user quits the application and it begins the transition to the background state. Use this method to pause ongoing tasks, disable timers, and throttle down OpenGL ES frame rates. Games should use this method to pause the game. */ NSLog(@"applicationWillResignActive"); } - (void)applicationDidEnterBackground:(UIApplication *)application { /* Use this method to release shared resources, save user data, invalidate timers, and store enough application state information to restore your application to its current state in case it is terminated later. If your application supports background execution, called instead of applicationWillTerminate: when the user quits. */ NSLog(@"applicationDidEnterBackground"); } - (void)applicationWillEnterForeground:(UIApplication *)application { /* Called as part of transition from the background to the active state: here you can undo many of the changes made on entering the background. */ NSLog(@"applicationWillEnterForeground"); } - (void)applicationDidBecomeActive:(UIApplication *)application { /* Restart any tasks that were paused (or not yet started) while the application was inactive. If the application was previously in the background, optionally refresh the user interface. */ NSLog(@"applicationDidBecomeActive"); } - (void)applicationWillTerminate:(UIApplication *)application { /* Called when the application is about to terminate. See also applicationDidEnterBackground:. */ NSLog(@"applicationWillTerminate"); } </code></pre>
    singulars
    1. This table or related slice is empty.
    1. POUse of background/foreground methods in AppDelegate
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCœur
    1. USAlan Zeino
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    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. VTUpMod
    1. COI understand when they are fired, what I don't understand is what concretely I would be able to write into these methods as I dont know which is the active ViewController.
      singulars
      1. PO
      1. USOliver
    2. COThere is no 'active' view controller, this is OO programming. The better question to ask is; "when one of these methods is fired upon my one-and-only app delegate, how do I ensure important classes know about it?". That, is a design issue and not a programming one. You might for example have Controller objects listening to Notifications fired within those app delegate methods, or you might just pass them to a Controller directly.
      singulars
      1. PO
      1. USAlan Zeino
    3. COI'm not sure to be ok with you. On my point of view it's really a question about what is actually displayed on the screen. Depending on what the user was doing when such events happens, the way you will manage them will differ. Or perhaps we are just saying the same thing with two different ways.
      singulars
      1. PO
      1. USOliver
 

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