Saagar Jha
(replying to ✾, chief troublemaker)
@millenomi @jrose @porglezomp @hikari Yeah so the lie here is that calling the superclass’s designated initializer is not actually going to provide a functional object because I do all that work in the convenience initializer
Kanbaru 🌟 (one hikari of too many)
(replying to Saagar Jha)
@saagar @millenomi @porglezomp @jrose btw interface builder can call init on your class if you prefer that to initWithCoder:, but I assume it can't connect outlets and stuff if you do (or can it 🤔)
1 replies →
1 replies
✾, chief troublemaker
(replying to Kanbaru 🌟 (one hikari of too many))
@hikari @saagar @porglezomp @jrose it will set your outlets anyway. but why use IB at this point when SwiftUI is just so much better on every important level
Kanbaru 🌟 (one hikari of too many)
(replying to ✾, chief troublemaker)
@millenomi @saagar @porglezomp @jrose what if i am coding for 2008's best mobile operating system. what then
2 replies →
2 replies
Kanbaru 🌟 (one hikari of too many)
(replying to Saagar Jha)
@saagar @millenomi @porglezomp @jrose begone, devil
Kanbaru 🌟 (one hikari of too many)
(replying to Kanbaru 🌟 (one hikari of too many))
@saagar @millenomi @porglezomp @jrose or, of course, set up a frame for a view, so this has questionable utility for actual views
Saagar Jha
(replying to Kanbaru 🌟 (one hikari of too many))
@hikari @millenomi @porglezomp @jrose The best views are ones that are hardcoded to support exactly one size
Kanbaru 🌟 (one hikari of too many)
(replying to Saagar Jha)
@saagar @millenomi @porglezomp @jrose [UIButton buttonWithType:UIButtonTypeInfoLight] my beloved