To clarify: Mike is of course correct that any class that doesn't have
an override of +automaticallyNotifiesObserversForKey: which returns no
for a given key, and that always sets values of that key in a
KVC-compliant manner, will generate KVO notifications for that key.
And there are many Cocoa classes that have not bothered to override
+automaticallyNotifiesObservesrForKey:. But one should *not* develop
the expectation that most, or even a substantial portion, of Cocoa is
KVO-compliant, because it is not.

--Kyle Sluder

On Tue, Jun 1, 2010 at 2:15 PM, Mike Abdullah <cocoa...@mikeabdullah.net> wrote:
> By default Cocoa classes use automatic KVO. So long as Cocoa always changes 
> the URL by calling -setFileURL: you will get proper notifications.
>
> On 1 Jun 2010, at 22:02, Jerry Krinock wrote:
>
>> There is no mention in -[NSDocument fileURL] documentation, nor in 10.5 or 
>> 10.6 release notes, that this property is observable using KVO.  But when I 
>> added some code to do this, created a document, and renamed the document in 
>> Finder while the document was open, my observer logged a hit.
>>
>> Is there some underlying or other documentation I don't know about?
>>
>> Jerry Krinock
>>
>>
>> - (void)observeValueForKeyPath:(NSString*)keyPath
>>                      ofObject:(id)object
>>                        change:(NSDictionary*)change
>>                       context:(void*)context {
>>    NSLog(@"2796: keyPath %@ observed:\n%@", keyPath, change) ;
>> }
>>
>> - (id)init {
>>    self = [super init] ;
>>    if (self != nil) {
>>        [self addObserver:self
>>               forKeyPath:@"fileURL"
>>                  options:NSKeyValueObservingOptionNew
>>                  context:NULL] ;
>>    }
>>
>>    return self ;
>> }
>>
>> - (void)dealloc {
>>    [self removeObserver:self
>>              forKeyPath:@"fileURL"] ;
>>
>>    ...;
>>    [super dealloc];
>> }
>>
>>
>> _______________________________________________
>>
>> 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/cocoadev%40mikeabdullah.net
>>
>> This email sent to cocoa...@mikeabdullah.net
>
> _______________________________________________
>
> 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/kyle.sluder%40gmail.com
>
> This email sent to kyle.slu...@gmail.com
>
_______________________________________________

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

Reply via email to