On Sep 14, 2015, at 16:06 , Carl Hoefs <email@hidden> wrote:
I guess I was exploiting undocumented/obsolete Xcode GUI behavior and getting away with it until now.
I think the missing information here is that in IB you’re working with abstractions, not Cocoa classes. In particular, note that when you drag what IB calls a (vanilla) View Controller onto the canvas, what it puts there is a *scene*, which doesn’t really exist. (It isn’t a Cocoa class, nor is it represented in your app as a specific object. AFAIK)
IB knows in which pairs of scenes you can drag segues between controllers (in your original way), and (vanilla) View Controller to View Controller isn’t one of the pairs.
A similar point came up recently in regard to bindings. From any given UI object and binding, you can only connect it to a few possible kinds of targets. That’s not because other bindings couldn’t be established by force in theory, but just that IB is protecting you from yourself.
(Cue PSA ending with kids waving at a smiling IB, “Thanks, IB!”)
|