• 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
Key-Value Binding and Threads
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Key-Value Binding and Threads


  • Subject: Key-Value Binding and Threads
  • From: King Chung Huang <email@hidden>
  • Date: Mon, 26 Mar 2007 22:10:50 -0600

Before everyone groans: No, I'm not asking if KVB is "thread-safe".

Searching on CocoaBuilder, the consensus seems to be that KVB is not "thread-safe" in terms of mutating a key on a thread other than the main thread and expecting UI changes to occur correctly. Would I be correct in deducing that KVO/KVB change notifications are processed on the thread where willChangeValueForKey: etc. is implicitly or explicitly called? i.e., if I mutate an observed value on thread B, then observers will be notified on thread B? Can I safely observe a key on object A from object B, if both objects are safe to mutate on the same thread?

Thanks,

King Chung Huang
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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


  • Follow-Ups:
    • Re: Key-Value Binding and Threads
      • From: Chris Kane <email@hidden>
  • Prev by Date: Re: Creating a bitmap of a scaled-down NSImage
  • Next by Date: NSHTTPCookieManagerCookiesChangedNotification ?
  • Previous by thread: Re: how do I access another Nib's controller?
  • Next by thread: Re: Key-Value Binding and Threads
  • Index(es):
    • Date
    • Thread