viewdidload

I am trying to set a global variable. In my case, just a boolean flag that indicates if a view is being presented for the first time: var initialLoadFlag: Bool = true After the view is presented, I want to set this flag to false: var initialLoadFlag: Bool = false And then check for it thenceforth: if initialLoadFlag { showWelcomeMessage() } So, I would like to create initialLoadFlag as a global variable. Where and how? I've tried: In the viewDidLoad area of my view controller In the application() method in my AppDelegate.swift file In the AppDelegate class No luck. I'm getting a Use of

Anyone know why this root View Controller's viewDidLoad is being called twice at launch? It's driving me nuts! here's the stack trace from first time through viewDidLoad : #0 0x0000276a in -[RootViewController viewDidLoad] at RootViewController.m:71 #1 0x3097548f in -[UIViewController view] #2 0x00002734 in -[RootViewController initWithCoder:] at RootViewController.m:39 #3 0x30ab5ce4 in -[UIClassSwapper initWithCoder:] #4 0x30514636 in _decodeObjectBinary #5 0x30514035 in _decodeObject #6 0x30ab5a1d in -[UIRuntimeConnection initWithCoder:] #7 0x30514636 in _decodeObjectBinary #8 0x30515f27 in

Is there anything similar to the viewDidLoad of UIViewController for a UIView ??? I need to be notified as soon as a UIView has loaded (Subclass of UIView ), and perform some actions. Costique Depending on what kind of actions you need to perform, there are several techniques: -(id)initWithFrame:(CGRect)frame - UIView's designated initializer; always sent to a UIView to initialize it, unless the view is loaded from a nib; -(id)initWithCoder:(NSCoder *)coder - always sent to initialize a UIView whenever the view is loaded from a nib; -(void)awakeFromNib - sent after all the objects in the nib

In Apple's scrollView example they don't call that. I always thought that's a must . Why should I call that anyways? If you are overriding the method you should still call the method in the super. Even if the super class is not doing anything with it today, Apple might one day change the implementation and your code will mysteriously stop working. If you really don't need to do anything in that method, leave it out of your code entirely, and the super's method will run as usual, without any intervention on your part. No, you don't need to call [super viewDidLoad]. Edit: But read below, because

I have always been a bit unclear on the type of tasks that should be assigned to viewDidLoad vs. viewWillAppear : in a UIViewController subclass. e.g. I am doing an app where I have a UIViewController subclass hitting a server, getting data, feeding it to a view and then displaying that view. What are the pros and cons of doing this in viewDidLoad vs. viewWillAppear ? LeonBrussels viewDidLoad is things you have to do once. viewWillAppear gets called every time the view appears. You should do things that you only have to do once in viewDidLoad - like setting your UILabel texts. However, you may

I have a pretty basic setup with a UINavigationController inside a UITabBarController. I'm wanting to programmatically layout the view of the rootViewController of that navcontroller, but when I look at self.view.frame inside viewDidLoad, I get this (in landscape , for example): 1. view frame: {{20, 0}, {748, 1024}} // looks like an odd portrait mode Then I autorotate to Portrait, and I get this: 2. view frame: {{0, 0}, {768, 911}} Then when I go back to Landscape, the frame is now this: 3. view frame: {{0, 0}, {1024, 655}} And further autorotation events will flip-flop between frame values #2