There are many different types of views that could be subclassed to make NibDesignable versions of them. The framework already includes many of them (UIView, UIControl, UITableViewCell, UITableViewHeaderFooterView, UICollectionViewCell, and UICollectionReusableView), but users may always have proprietary classes that may benefit from being subclassed.

Subclassing views within the framework is made trivial by the abstraction of NibDesignableProtocol and it's default implementation. However, the scoping of -setupNib() makes it difficult to do outside of that file. If the scope of that method were expanded to public (instead of fileprivate) it would greatly ease this task. Are there any obvious down sides to doing this?

Hi,

thank you for your awesome view.

I did managed to make your library working once but is is not working anymore.

I set the file owner to my custom view
I let the main UIView as an UIView
I named the xib to the same name as the class.

The only thing I changed is that I used custom live rendering view inside my xib (Those views don't use xib file so it renders well in the xib).

Do you have any idea ?

Here is the code :

import UIKit

class HeaderFicheClientView: NibDesignable {

@IBOutlet weak var nameCustomer: UILabel!

@IBInspectable internal var nameText:String = "Nathalie Beaudry"{
    willSet{
        nameCustomer.text = nameText
    }
}

@IBInspectable internal var borderColor:UIColor = UIColor.blackColor(){
    willSet{
        self.layer.borderColor = borderColor.CGColor
        self.layer.borderWidth = 1
    }
}

}

Is it possible to add support for Swift Package Manager?

Incorrect:

Correct:

My custom view from NibDesignable is crashing on line 64 of NibDesignable.swift

    // MARK: - NSCoding
    required public init(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)  // line 64
        self.setupNib()
    }

with EXC_BAD_ACCESS(code=2) when the view gets instantiated at run time. Placing breakpoints on the line suggests an infinite loop of sorts where the initializer gets called over and over again.

I am currently debugging in a bare project and have also stripped my custom class to a bare skeleton as:

import UIKit
import NibDesignable

class CustomView: NibDesignable {
}

Any ideas?

Swift doesn't allow overriding a method in an extension. The fastest way to fix is adding @objc to the method:

extension UIView {
    @objc public var nibContainerView: UIView {
        return self
    }
    /**
     Called in the default implementation of loadNib(). Default is class name.

     - returns: Name of a single view nib file.
     */
    open func nibName() -> String {
        return type(of: self).description().components(separatedBy: ".").last!
    }
}

I don't have permission to make a PR, so please help release new version including that update.

Thanks & Best Regards,

A new release needs to be cut for Carthage to recognize the latest updates.

It seems that using NibDesignableTableViewCells does not work when using automatic cell height on the tableView. In my project I have a tableviewclass, subclass of NibDesignableTableViewCell, all set up hunky dory. The UI shows up (which is great), but it is squished (not so great). At first I thought this was due to using StackViews, but this was not the case (I have a very simple tableViewCell with just a label inside). I attached an image. The first cell is a nib designable cell (and it is squished, the ones below it ended up having a similar layout until I stopped them being a nib designable. My guess is that the issue comes when adding the view to the content view (lines 101-107) and how automatic heights are calculated.

I have a fairly complex view hierarchy in a UITableViewCell (among other things) that uses nested NibDesignables. On slower devices the load time is very noticeable. For example, with 2 NibDesignables each with 5 subviews that are NibDesignable, it takes approximately 2 seconds on the main thread. Profiler doesn't show a large CPU burden, though.

Thoughts? Are there any easy fixes to make this kind of hierarchy instantiate faster? If I can't fix this then I'm afraid I'll be forced back to writing all of my views/autolayout programmatically. :-(

Hello everyone.

I'm struggling with @IBDesignable UITableViewCells.

When I create a tableViewCell, it 's possible to change the background color of the cell to red:

But I can't see my label, and I can't update the text of the label.

Could someone make an example for at custom table view cell with a label, or explain how to update my custom designable table view cell?

Thank you!

Some developers take issue with setting FilesOwner to a UIView subclass. Is there any way around this to make NibDesignable more palatable to purists?

XCode will says warning: IB Designables: Ignoring user defined runtime attribute for key.

I founded that before I get crazy, please add it to README.

First i must say that the NibDesignable class is awesome.

I've created a subclass called LineField which contains a UITextField with a line under it.
when I plug in my LineField into my Storyboard, I wanted to be able to connect an IBOutlet on my UIViewController to the LineField's text field. but unfortunately that doesn't seem possible.
Is there a way to do that which I'm not aware of ?

@IBDesignable
public class LineField: NibDesignable {

    @IBOutlet weak var textField: UITextField!
    @IBOutlet weak var lineView: UIView!

    @IBInspectable public var lineColor: UIColor = UIColor.lightGrayColor() {
        didSet {
            self.lineView.backgroundColor = lineColor
        }
    }

    override public func awakeFromNib() {
        super.awakeFromNib()
    }

}

My ViewController:

class TextQuestionEditVC: UIViewController {

    @IBOutlet weak var saveButton: UIBarButtonItem!
    @IBOutlet weak var questionLineField: LineField!
    @IBOutlet weak var searchField: UITextField!

}

TLDR: how do i connect my searchField to the LineField->textField ?

Just like title, CustomControl is subclass of NibDesignableControl, and in storyboard I connect the "Touch Up Insede" of CustomControl to viewcontroller, the action doesn't fired.

Sorry I'm a starter, can you write a works fine NibDesignableControl for UIControl? Thanks

I am not sure if this issue is because of a tableviewcell or something I missed in the documentation. I can't seem to get a TVC to work in a Nib file once I add AutoLayoutConstraints.

While it's debatable how long ObjC is going to be around, it's certain that it'll be with us for the next year, very very likely much longer. Because in many projects one doesn't have a free choice which language to use, it'd be great if NibDesignable would support Swift and ObjC. At the moment NibDesignable requires subclassing which is only supported within Swift and from an ObjC baseclass to a Swift subclass, not the other way round, wich makes it impossible to use NibDesignable in ObjC projects.

It'd be great to either find another way how NibDesignable could work that does not require subclassing or port the library to ObjC. I guess the latter is a bit unpopular, but it's the right move in my opinion. I'd volunteer to do the work.

I am implementing UICollectionViewCell the same way I would a regular UIView with NibDesignable but I can't get it to work. Always getting errors similar to this class is not key value coding-compliant for the key randomLabel.

why not use ??
{
return String(self.dynamicType)
}
??

I imported the file NibDesignable in my project, followed the readme guidelines, but I get an error when the views are refreshed:

error: IB Designables: Failed to render and update auto layout status for ViewController (BYZ-38-t0r): The agent threw an exception.

I send my project as attachment.
ViewFromXib.zip

I have a UITableViewCell that contains two UIView both extending NibDesignable.

In each of those view I have an initializer like the following.

required init?(coder aDecoder: NSCoder) {
	super.init(coder: aDecoder)
		
	setup()
}

This init triggers

// MARK: - NSCoding
    required public init?(coder aDecoder: NSCoder) {
        super.init(coder: aDecoder)
        self.setupNib()
    }

of NibDesignable.
Then everytime this line gets called

```return nib.instantiate(withOwner: self, options: nil)[0] as! UIView // swiftlint:disable:this force_castit calls myrequired init?

 and I end up having an infinite loop.

I used the same type of initialisation in another view (not in a table view cell) and it works fine.

Any idea what's wrong?

Thanks

Hey @mbogh, how about adding more maintainers to the project? You've collected nearly 200 stars, now would be a great time to add more people to ensure it's development doesn't stale. Maybe @farzadshbfn, @ggrana or @Jachobsen are interested?

Would love to see this lib being actively maintained!

I have a UITableViewCell that I would like to make Designable. How can I do?

Because as soon as I extend NibDesignable, it obviously stops being a UITableViewCell.

I downloaded the demo project and run it. On the device/simulator it works fin but when I open the Storyboard, the view stays blank.

In the identity inspector, Designables is always Updating.

Does it happen to someone else?

I haven't touched anything on the project.

I found a bug where if a view inherits from NibDesignable, layoutSubviews gets called with the original sizes from the nibs but not for subsequent resizes. I noticed it when I was making a circular image view and despite doing self.imageView.layer.cornerRadius = self.imageView.frame.size.width /2 in layoutSubviews, the image was rounded strangely, even when it had a 1:1 aspect ratio using autolayout.

My fix was simply to add self.layoutIfNeeded to awakeFromNib but I suspect the issue goes deeper than that.

I inherited my custom view from NibDesignable and it crashes on following lines:
super.init(coder: aDecoder)