• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: KVO, which thread?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KVO, which thread?


  • Subject: Re: KVO, which thread?
  • From: Mike Abdullah <email@hidden>
  • Date: Mon, 04 Feb 2013 22:35:29 +0000

On 4 Feb 2013, at 21:44, Todd Heberlein <email@hidden> wrote:

> I have an NSInvocationOperation, anOp, and register to observe when its isFinished variable is set
>
> [anOp addObserver:self forKeyPath:@"isFinished" options:NSKeyValueObservingOptionNew context:NULL];
>
> When my operation is done, isFinished is set, and thus my method -observeValueForKeyPath:ofObject:change:context: is called, which thread is it being called on? The main thread, or the thread created to process the NSInvocationOperation?

Unless something in NSOperation goes out of its way to deliver the notification on a particular thread, the answer is: whichever thread caused the KVO notification to be fired.


_______________________________________________

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:

This email sent to email@hidden

References: 
 >KVO, which thread? (From: Todd Heberlein <email@hidden>)

  • Prev by Date: Re: KVO, which thread?
  • Next by Date: Re: NSOperation communicating progress?
  • Previous by thread: Re: KVO, which thread?
  • Next by thread: Do CALayer filters apply to non-image drawing?
  • Index(es):
    • Date
    • Thread