> On May 1, 2015, at 08:58 , Fritz Anderson <fri...@manoverboard.org> wrote: > > I almost devoted half-a-chapter to how disastrous and inexplicable this is, > until I figured out the rules. Part of the rant made it through to the page > proofs (print minus one). > > Storyboards are not monoliths at runtime, they’re an archive of NIBs, one for > each view controller. Cross-controller relationships are missing only in the > sense that they are impossible. That includes parent-child relationships from > window controllers across split-view controllers. > > A window controller has a reference to its content controller. Descend that > into the split-view controller and index the splits, then recover the content > controller for each. In the process, you can propagate the child controllers > up to the window controller (or whatever).
I'm not sure I agree that it's impossible. They just need to build the support for it. A connection in IB is just a fancy way of setting a property in one XIB to a string value. I can envision dragging from a property in one view controller to another view controller (or property within another view controller). If those two view controllers share a common ancestor in the view controller containment hierarchy, THAT VC would have properties set indicating which controllers it should auto-wire. Honestly it doesn't even seem that difficult to implement for the engineers familiar with the Storyboard and NIB loading subsystem. -- Rick Mann rm...@latencyzero.com _______________________________________________ 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
