On Jan 3, 2010, at 14:56, Rick Mann wrote: > Is -exposeBinding: only necessary when implementing an IB plug-in? Or is it > required to make bind: work at all (on a custom object)? I find two slightly > conflicting statements in the docs about this.
I can't speak definitively, but I believe the answer lies somewhere in the middle. You don't actually need to expose bindings to make them work, but if you want to have your bindings established automatically during nib loading they'll need to be exposed to IB. Whether an IB plug-in is the only way to make IB aware of an exposed binding, or whether there's an alternate mechanism (by analogy with action methods, where IB can find them by looking at header files, but you can still "declare" them explicitly within IB if necessary), I don't know. OTOH I don't think there's any point to defining new bindings at all, unless you want to make them generally available to users who are not working at the source code level, or unless you going to use them so much that it's worth being able to hook them up in IB rather than code. In that case, you'd want the plug-in anyway. (For one-off use, ad-hoc coding using KVO is probably sufficient.) FWIW. _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
