Re: What to use observeValueForKeyPath: context

• Subject: Re: What to use observeValueForKeyPath: context
• From: Jim Correia <email@hidden>
• Date: Fri, 29 Aug 2008 12:44:22 -0400
• Delivered-to: email@hidden
• Delivered-to: email@hidden

On Aug 29, 2008, at 10:56 AM, Dave Dribin wrote:

It seems that KVO best practice is to use the "context" in observeValueForKeyPath:ofObject:change:context: to differentiate between different key paths, rather than check key path strings for equality. Since context is a void *, it also seems best practice to just use some unique pointer values. For example, mmalc's Graphics Bindings sample does this:

static void *PropertyObservationContext = (void *)1091;
static void *GraphicsObservationContext = (void *)1092;
static void *SelectionIndexesObservationContext = (void *)1093;

Your KVO context has to be unique.

Jim

_______________________________________________

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

• 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