You're welcome! Glad to be helpful :)
Tadeas
On Mon, Oct 10, 2016 at 9:12 PM Lou Zell wrote:
> Tadeas - Just what I was looking for. Thank you!
>
> class BaseView: UIView {
> @available(*, unavailable)
> required init?(coder aDecoder: NSCoder) {
> fatalError("Not implemented!")
Tadeas - Just what I was looking for. Thank you!
class BaseView: UIView {
@available(*, unavailable)
required init?(coder aDecoder: NSCoder) {
fatalError("Not implemented!")
}
}
On Mon, Oct 10, 2016 at 11:45 AM, Tadeas Kriz wrote:
> Lou, you can create a "class BaseView: U
Lou, you can create a "class BaseView: UIView" which will serve as a
default view your views will subclass and inside it, add the init required
by NSCoding, make its body `fatalError("Not implemented!")` and add the
following attribute on the init: `@available(*, unavailable)`. Then you'll
not need
This is a wrong place to ask. This topic is part of the iOS SDK from Apple not
part of Swift itself or libraries like Foundation.
--
Adrian Zubarev
Sent with Airmail
Am 8. Oktober 2016 um 18:32:50, Lou Zell via swift-users
(swift-users@swift.org(mailto:swift-users@swift.org)) schrieb:
>
> O
Oh wow, I stumbled on this immediately after posting: For anyone else that
fills their NSCoding initializers with assert(false), switch them to
fatalError("message")
On Sat, Oct 8, 2016 at 9:22 AM, Lou Zell wrote:
> Hi all,
>
> For better or worse I still hand code most of my views. I am getting
Hi all,
For better or worse I still hand code most of my views. I am getting
frustrated by the constant compiler error that I haven't updated "required
init(coder:)", which is something that will never be executed in my case.
Is there some hacky mechanism that I could use to create a subtype that
