Right overall picture, wrong implementation details in the first paragraph. A “First Responder” in a NibFile is an Object … No, actually, First Responder is nil. Connecting a UI control (e.g., button) to First Responder in a nib is equivalent to [control setTarget:nil] in code. The reason for the First Responder fake-object in the nib … Read more
Macro #define AssertFileExists(path) NSAssert([[NSFileManager defaultManager] fileExistsAtPath:path], @”Cannot find the file: %@”, path) #define AssertNibExists(file_name_string) AssertFileExists([[NSBundle mainBundle] pathForResource:file_name_string ofType:@”nib”]) Here are a set of macros that you can call before you try an load a .xib or .nib, they will help identify missing files and spit out useful message about what exactly is missing. Solutions Objective-C: … Read more
I filed a bug report a week or two ago – in short, they’re aware of it. I won’t paste the email here as it said it was under NDA. Here’s hoping for 4.0.3 or similar with some zooming 🙂
I found a much better way that works independent of the nav controller. Right now, I have this working when embedded in a nav controller, and when NOT embedded (although I’m not using the nav controller right now, so there may be some bug I’ve not seen – e.g. the PUSH transition animation might go … Read more
That’s expected, because the IBOutlet(s) are not assigned by the time the initializer is called. Instead of calling commonInit() in init(coder:), do that in an override of awakeFromNib as follows: // … required init(coder aDecoder: NSCoder) { super.init(coder: aDecoder) } override func awakeFromNib() { super.awakeFromNib() commonInit() } // …
It’s a very similar question to ios setContentOffset not working on iPad … And my answer is the same as there: “You should not initialise UI geometry-related things in viewDidLoad, because the geometry of your view is not set at this point and the results will be unpredictable. … viewWillAppear: is the correct place to … Read more
Version 4.6.3 of Xcode resolves this issue. However, as the comments state, you all need to be running that same version. If four developers are on 4.6.3, and one is on a previous version, then that developer will experience the same issue. However, if they do not commit that change then it will not affect … Read more
XIB’s are very cool. they are basically an un-compiled NIB (in XML format if memory serves me) during the build process they are converted to NIB’s to be deployed in the final product.
I had this same issue and fixed it by unchecking the ‘Use Autolayout’ checkbox on the Document Inspector pane in Utilities.