On Jun 19, 2017, at 11:31 , Dave <d...@looktowindward.com> wrote: > > I think it would be better to move to NIBs now before wasting anymore time > trying to get Storyboards to work.
I don’t honestly understand why you think this is going to make anything easier. With storyboards, you *are* using NIBs, behind the scenes. Everything is architecturally the same as starting from XIB files, except in a couple of minor areas (e.g. in code you instantiate view controllers from the storyboard instead of creating them directly). Plus, with a storyboard you can wire up segues instead of having to figure out how to do the particular transition using one of a bewildering array of methods. Either way, you’re going to have to learn at some point how the view controller hierarchy works, which entirely separate from how the view hierarchy works, and has nothing much to do with how complex your views are. (That’s what I assumed “I only have one fairly complex view controller” meant, since one view controller is not a complicated VC hierarchy. Putting that VC in a XIB file still gives you the same one-VC hierarchy, and you still are no closer to a solution to your problems.) I know it’s frustrating, and I’m no expert on this, but I think there is an “Aha!” moment when you figure out that storyboards are not in fact magic (or perhaps, in your current scenario, not in fact out to screw you), and the view controller thing just falls into place. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
