NSStoryboard’s Quirks and Features
Storyboards are ill suited for parent-child connections. Only builtin container controllers, such as NSTabViewController, allow them with very few customizable options. Custom segues invoked from code can still be used to encapsulate transitions between child view controllers.
When loaded from a storyboard NSTabViewController, contrary to the documentation, loads all its children and their views.
Controller-less views (such as Main Menu and Status Item Menu) use NSApp’s delegate as a source controller. It can implement any of the NSSeguePerforming protocol methods.
It’s pointless to connect multiple builtin segues to the same Single-presenting controller: once it’s displayed nor segue nor any of the NSSeguePerforming are called. In other hand, custom segues are completly oblivious of that setting and are always performed.
