[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: An object should not retain its delegate, but what about its data source ?

Subject: Re: An object should not retain its delegate, but what about its data source ?
From: Nick Zitzmann <email@hidden>
Date: Tue, 31 Jul 2007 16:05:15 -0600
Delivered-to: email@hidden
Delivered-to: email@hidden


On Jul 31, 2007, at 3:27 PM, Erik Buck wrote:

Should an object retain its data source ?

No. Why would it do that? I thought the main reason why data sources are separate from delegates is so one class can provide data and another class can react to events if the developer wishes to split them up.

Do NSBrowser and NSTableView retain their data sources ?


That's a trick question; NSBrowser doesn't have a data source.

Nick Zitzmann
<http://www.chronosnet.com/>

_______________________________________________

Cocoa-dev mailing list (email@hidden)

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/email@hidden

This email sent to email@hidden

References:
	>An object should not retain its delegate, but what about its data source ? (From: Erik Buck <email@hidden>)

Prev by Date: Re: applicationWillTerminate and NSDocumentController
Next by Date: Re: Using -interpretKeyEvents in NSTextView to interpret key events
Previous by thread: An object should not retain its delegate, but what about its data source ?
Next by thread: Re: An object should not retain its delegate, but what about its data source ?
Index(es):
- Date
- Thread

Home