EDIT: Several commenters have claimed that more recent versions of Xcode return IBOutletCollections in the order the connections are made. Others have claimed that this approach didn’t work for them in storyboards. I haven’t tested this myself, but if you’re willing to rely on undocumented behavior, then you may find that the explicit sorting I’ve … Read more
This is what Outlet Collections are for. Drag all your textfields in the same Outlet Collection in InterfaceBuilder and create an @IBOutlet to that collection in your class file: To create the outlet collection in InterfaceBuilder, ctrl-drag from the first UITextField to your class file in the assistant editor. Then choose Outlet Collection: ctrl-drag the … Read more
UPDATE: As of Xcode 4.6 (possibly earlier) you can now create outlets by control-dragging! – This has to be done into an interface section or class extension (the class extension doesn’t exist by default for new cell subclasses. Thanks to Steve Haley for pointing this out. You can’t get the outlet automatically connected and created … Read more
Here are some things that can fix this (in increasing order of difficulty): Clean the project (Product > Clean) Manually paste in @IBOutlet weak var viewName: UIView! // or @IBAction func viewTapped(_ sender: Any) { } and control drag to it. (Change type as needed.) Also see this. Completely close Xcode and restart your project. … Read more
When you attach a button to the viewController and create an action (IBAction) using ctrl-drag, you create a method that looks likes this in Swift (if it doesn’t have arguments): @IBAction func buttonAction() {} In Objective-C the same thing will look like this: – (IBAction)buttonAction {} So that means that @IBAction func OK(sender: UIButton){} is … Read more
Use the Connections inspector to break the connection. Then you can modify/delete the object and/or the code without having to worry.
Update: This works properly in Xcode now – “Outlet Collection” is one of the connection options in Interface Builder, which creates something that looks like: @IBOutlet var labelCollection: [UILabel]! While we’re waiting for a fix, you can approximate this using a computed property. Let’s say my view has five UILabels that I want in a … Read more
Typically this happens because your view controller hasn’t loaded its view hierarchy yet. A view controller only loads its view hierarchy when something sends it the view message. The system does this when it is time to actually put the view hierarchy on the screen, which happens after things like prepareForSegue:sender: and viewWillAppear: have returned. … Read more
IBAction and IBOutlet are macros defined to denote variables and methods that can be referred to in Interface Builder. IBAction resolves to void and IBOutlet resolves to nothing, but they signify to Xcode and Interface builder that these variables and methods can be used in Interface builder to link UI elements to your code. If … Read more