Delegates *are* often automatically registered for their delegated
object's notifications, however. The differences between these and
"regular" delegate methods should be apparent in the documentation,
though, since the former will take a single argument of NSNotification
*.
(To help the OP, not for I.S. ;) )
On May 19, 2008, at 12:01 PM, I. Savant wrote:
On Mon, May 19, 2008 at 12:52 PM, Michael Vannorsdel <[EMAIL PROTECTED]
> wrote:
Delegates act like observers. They register with another object
saying
"hey, if you do something important I want to know about it and
have a
chance to act on it too".
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.
--
I.S.
_______________________________________________
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/nateweaver%40xtechllc.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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]
