Indeed. I was just trying to keep it in simple terms as not to
overwhelm the OP with heavy details. I just wanted the concept to
make some sense in better known terms at the risk of oversimplifying.
On May 19, 2008, at 11:01 AM, I. Savant wrote:
Well, no, not really. This is significantly different in that you
can set an object as another object's delegate, but if it (your custom
object acting as a delegate) doesn't respond to a particular delegate
method, the delegating object will not call the method. In this way,
you can set objA as objB's delegate and implement none of objB's
delegate methods in objA ... so none will be called.
_______________________________________________
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 [EMAIL PROTECTED]
