• 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: What to use observeValueForKeyPath: context
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What to use observeValueForKeyPath: context


  • Subject: Re: What to use observeValueForKeyPath: context
  • From: Keith Duncan <email@hidden>
  • Date: Fri, 29 Aug 2008 17:43:08 +0100

After all, what prevents somebody else from using 1091 too?

Nothing whatsoever. But that isn't a problem. So long as the observation context remains internal it doesn't have to be universally unique.


If you're performing [anotherObjectNotSelf addObserver... then yes, I'd make sure that the context is unique, so that it doesn't conflict with an internal context.

Keith
_______________________________________________

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


  • Follow-Ups:
    • Re: What to use observeValueForKeyPath: context
      • From: Jim Correia <email@hidden>
References: 
 >What to use observeValueForKeyPath: context (From: Dave Dribin <email@hidden>)
 >Re: What to use observeValueForKeyPath: context (From: "Michael Ash" <email@hidden>)

  • Prev by Date: Re: What to use observeValueForKeyPath: context
  • Next by Date: Re: What to use observeValueForKeyPath: context
  • Previous by thread: Re: What to use observeValueForKeyPath: context
  • Next by thread: Re: What to use observeValueForKeyPath: context
  • Index(es):
    • Date
    • Thread