iboutlet

I am learning Stanford CS193p course with Xcode 4.3.3. I think the screenshot below is pretty much self-explaining. But i will describe the problem with words anyway. I control-drag a UILabel from storyboard to corresponding implementation file to make the IBOutlet @property. Then I see two connections displayed when clicking the filled circle in the left side of the editor where shows line numbers. I don't know how to delete it. Moreover, I see only ONE connection in storyboard's connections inspector of the UIlabel. More weird, when I try to set the UILabel's text inside the setter of a

I am using a storyboard to get the correct height of a navigation bar in my launch image . However, after customizing the view controller a bit, it now displays a black screen instead of a launch image. When I set it to a brand new view controller, everything is fine. It seems like the original view controller is now in a bad state. How can I fix this? (I'm running iOS 8.2 simulator on Xcode 6.2.) The problem in this case was that there was an outlet set on the view controller . If there are any outlets on the initial view controller (or, if the initial view controller is a navigation

I am calling a class function from my ViewController class like this: Buttons.set_cornerRadius(10) I have another .swift file where I have the function declared: class Buttons { class func set_cornerRadius(radius: CGFloat) { ViewController().someButton.layer.cornerRadius = radius } } When I'm trying to run this it throws the error: "Unexpectedly found nil while unwrapping an optional Value" . I checked the Storyboard-IBOutlet connections already. Everything is connected right. If I call the method in the same class like this, everything works: class ViewController: UIViewController { @IBOutlet

What are the reasons why an IBOutlet (connected) could be nil ? I have one in may application which is always nil , even if I recreate everything from scratch (declaration and control). It could be that your nib is messed up, but I find a common reason is having two instances where you think you only have one, and the one you're using in your code is not the one you connected. If you've also defined a loadView method that creates the view, it is possible based on how you initialize it. If you initialize it using alloc-init and the nib name is not the same as class name, then you can have a

I've been reviewing the Apple docs and sample code to try to determine the best way to manage memory for IBOutlets. I'm a little confused, to say the least. The CurrentAddress sample code declares IBOutlets as properties: @interface MapViewController : UIViewController <MKMapViewDelegate, MKReverseGeocoderDelegate> { MKMapView *mapView; UIBarButtonItem *getAddressButton; } @property (nonatomic, retain) IBOutlet MKMapView *mapView; @property (nonatomic, retain) IBOutlet UIBarButtonItem *getAddressButton; Great. And these are released in dealloc: - (void)dealloc { [mapView release];

The sample code linked here works great and allows a UIScrollView to display images with paging and preview of the images before and after the current image: http://blog.proculo.de/archives/180-Paging-enabled-UIScrollView-With-Previews.html https://github.com/alexrepty/Paging-Enabled-UIScrollView-With-Previews I'm trying to encapsulate the example in a single control that can be reused. So I created a PagingScrollView: @interface PagingScrollView : UIView { IBOutlet UIScrollView * scrollView; } @property (nonatomic,retain) IBOutlet UIScrollView * scrollView; @end with dirt simple

I have a specific method that accepts a UIView object, and I want to pass objects to it that can be of one of two classes. So say it accepts a UIView that represents an animal, I want to be able to pass a DogView and a CatView or other animal-type classes potentially. Within that method I want to set the nameLabel view, which all animals have. How do I set it up so I'd be able to do this? My first reaction was to have a super class (such as AnimalView ) that has the nameLabel variable on it, and then subclass it for each new animal. However, if I want the nameLabel to be an outlet, it doesn't