On Apr 8, 2016, at 08:53 , David Catmull <davidcatm...@gmail.com> wrote: > > I don’t see any additional nib files in the application package.
It may not be a separate file, it may just be archived data that’s loaded as if a NIB file. Note that it is possible to register a custom NIB for a particular cell identifier, and I assume the regular mechanism (where the cell is designed into the table in IB) uses much the same technique underneath. I’m speculating about this implementation because you asked why Xcode might object to the connection you tried to set up. >> Perhaps "it works as is” because there’s actually no target, so the action >> message passes up the responder chain to the view controller. In that case, >> there isn’t any need to find a way to specify the target explicitly. > > From what I see in the debugger, that doesn’t seem to be happening, although > it goes through something called os_activity_initiate and I suppose it’s > possible the responder chain is being traced in there. You said it works as is, with a warning. I’m suggesting it works because there’s no target in the built output of this IB file. The scan of the responder chain (for an object that implements the action method) is likely a loop inside the frameworks, so I doubt you’d see it happen in the debugger. You could verify this by simply removing the target connection that’s causing the warning, and see if the action method still ends up in the right place. Or, turning the question around, why do you need a target at all, since the view controller is going to be in the responder chain (in OS X 10.10+, at least)? _______________________________________________ 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
