No idea whether this is of use but an example of two logically unconnected controllers talking to each other via notifications can be found here.
That's certainly a way to accomplish one-way messaging "whenever it gets there", but it's not always appropriate. Notifications do not occur within the same run loop, so this method wouldn't work if you needed to, say, tell another controller to modify something before continuing to "the next step". Additionally, how can you "ask" the controller for something (like its current selection)?
Just some things to consider. -- 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/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
