Home > Articles > Programming > General Programming/Other Languages

  • Print
  • + Share This
This chapter is from the book

This chapter is from the book

Collaboration of Patterns Within Bindings and Controllers

Once the behavior of binding has been explained, programmers commonly want to know how bindings work. Although bindings are an advanced topic, there's really no magic. Interface Builder sends -(void)bind:(NSString *)binding toObject:(id)observableController withKeyPath:(NSString *)keyPath options:(NSDictionary *)options messages when it establishes bindings, and you can send the same messages to establish bindings programmatically.

Key Value Coding and Key Value Observing technologies underlie bindings. Key Value Coding is briefly described in Chapter 19 and again in Chapter 30, "Core Data Models." It is a variation of the Associative Storage pattern, which lets you access the properties of objects as if every object were a simple dictionary of key/value pairs. See Apple's conceptual documentation for Key Value Coding at http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueCoding/KeyValueCoding.html. Key Value Observing is a variation of the Notification pattern from Chapter 14, "Notifications." Key Value Observing monitors the values of object properties on behalf of other objects that are interested observers. The underlying implementation of Key Value Observing is somewhat different from the Notification pattern, but in essence, Key Value Observing serves the same function: Register to receive messages when something of interest happens. Apple's conceptual documentation for Key Value Observing is at http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueObserving/KeyValueObserving.html.

Key Value Observing is implemented by the NSKeyValueObserving informal protocol, which adds methods to NSObject from which almost all Cocoa objects inherit. Hidden deep behind the scenes, Cocoa maintains a collection of some kind that lists all of the objects that currently observe other objects' properties. Apple is deliberately vague about the specific implementation of that collection because it wants to preserve the flexibility to change the implementation in the future. You add an object to the list of objects that observe a property by calling NSKeyValueObserving's -addObserver:forKeyPath:options:context: method. To remove an observer from the list, use NSKeyValueObserving's -removeObserver:forKeyPath:.

What Happens in -bind:toObject:withKeyPath:options:?

Sending the -bind:toObject:withKeyPath:options: message to an object creates a bi-directional set of Key Value Observing associations. Somewhere inside Apple's -(void)bind:(NSString *)binding toObject:(id)observableController withKeyPath:(NSString *)keyPath options:(NSDictionary *)options implementation, the following code or something similar is executed:

[self addObserver:observableController forKeyPath:binding
   options:(NSKeyValueObservingOptionNew|NSKeyValueObservingOptionOld)
   context:nil];

[observableController addObserver:self forKeyPath:keyPath
   options:(NSKeyValueObservingOptionNew|NSKeyValueObservingOptionOld)
   context:nil];

There isn't much more involved with the establishment of bindings. Apple documents the available options at http://developer.apple.com/documentation/Cocoa/Reference/ApplicationKit/Protocols/NSKeyValueBindingCreation_Protocol/Reference/Reference.html. If a key path has multiple '.' separated properties, -bind:toObject:withKeyPath:options: adds observers for all of the individual properties in the path as needed. You can get information about existing bindings via the -(NSDictionary *)infoForBinding:(NSString *)binding method. Sending the -(void)unbind:(NSString *)binding message results in corresponding calls to NSKeyValueObserving's -(void)removeObserver:(NSObject *)anObserver forKeyPath:(NSString *)keyPath method.

Given that bindings are a relatively thin veneer on Key Value Observing, the magic of bindings resides within Key Value Observing.

How Does Key Value Observing Detect Changes to Observed Properties so That Observing Objects Can Be Notified?

The answer is that changes to observed properties need to be bracketed by calls to -(void)willChangeValueForKey:(NSString *)key and -(void)didChangeValueForKey:(NSString *)key. If you write your own code to programmatically modify the values of observed properties, you may need to explicitly call -willChangeValueForKey: and -didChangeValueForKey: like the following method that sets the "counter" property without calling an appropriate Accessor method:

- (void)incrementCounterByInt:(int)anIncrement {
[self willChangeValueForKey:@"counter"];
counter = counter + anIncrement;
[self didChangeValueForKey:@"counter"];
}

Inside NSObject's default implementation of the NSKeyValueObserving informal protocol, -willChangeValueForKey: and -didChangeValueForKey: are implemented to send messages to registered observers before and after the property value changes.

It's not necessary to explicitly call -willChangeValueForKey: and -didChangeValueForKey: within correctly named Accessor methods. When you use Objective-C 2.0's @synthesize directive to generate Accessor method implementations, the details are handled for you. Even if you hand-write Accessor methods, Cocoa provides automatic support for Key Value Observing through a little bit of Objective-C runtime manipulation briefly described at http://developer.apple.com/documentation/Cocoa/Conceptual/KeyValueObserving/Concepts/KVOImplementation.html. At runtime, Cocoa is able to replace your implementation of each Accessor method with a version that first calls -willChangeValueForKey:, then calls your implementation, and finally calls -didChangeValueForKey:.

When Key Value Coding's -(void)setValue:(id)value forKey:(NSString *)key or -(void)setValue:(id)value forKeyPath:(NSString *)keyPath methods are used to modify an observed property, the appropriate Accessor methods (if any) are called, and the Accessor methods take care of calling -willChangeValueForKey: and -didChangeValueForKey:. If there aren't any available Accessor methods, -setValue:forKey: and -setValue:forKeyPath: call -willChangeValueForKey: and -didChangeValueForKey: directly. In summary, you only need to explicitly call -willChangeValueForKey: and -didChangeValueForKey: if you change the value of an observed property without using Key Value Coding and without using an appropriately named Accessor method.

What Message Is Sent to Notify Registered Observers When an Observed Property's Value Is Changed?

By default, the -didChangeValueForKey: method sends the - (void)observeValueForKeyPath:(NSString *)keyPath ofObject:(id)object change:(NSDictionary *)change context:(void *)context message to all registered observers after an observed property changes value. You can configure the -willChangeValueForKey: method to send notification before each change if you specify the NSKeyValueObservingOptionPrior option in the options: argument used to register an observer. The options: argument also governs whether the change notification includes only the previous value, only the new value, or both the old and new values.

Most Cocoa View subsystem classes already implement -observeValueForKeyPath: ofObject:change:context:. You need to implement that method in your custom View objects if you want them to work correctly with bindings. You may also need to implement -observeValueForKeyPath:ofObject:change:context: in model objects if you want to perform special logic whenever observed properties change. Unfortunately, implementing -observeValueForKeyPath:ofObject:change:context: is one of the least elegant aspects of using Cocoa.

You almost invariably have to implement -observeValueForKeyPath:ofObject:change:context: by using string comparisons to determine what logic to invoke based on which key path changed. The following code is a trivial example implementation of -observeValueForKeyPath:ofObject:change:context::

- (void)observeValueForKeyPath:(NSString *)keyPath
   ofObject:(id)object change:(NSDictionary *)change
   context:(void *)context
{
   if ([keyPath isEqualToString:@"floatValue"]) {
      NSNumber   *newValue = [change
         objectForKey:NSKeyValueChangeNewKey];
      if(0.0 > [newValue floatValue]) {
         // Perform special logic for negative values here
      }
      [self setNeedsDisplay:YES];
   }

   // be sure to call the super implementation
   [super observeValueForKeyPath:keyPath
      ofObject:object change:change
      context:context];
}

The need to perform explicit string comparisons like [keyPath isEqualToString: @"floatValue"] in -observeValueForKeyPath:ofObject:change:context: is inelegant. It's easy to imagine an implementation of -observeValueForKeyPath: ofObject:change:context: that has to perform hundreds of string comparisons after every observed property change to control application logic. Objective-C selectors and the Perform Selector pattern from Chapter 9 exist to make string comparisons in branch logic unnecessary. It's unfortunate that Apple didn't take advantage of the pre-existing patterns like NSNotification and the use of selectors when implementing Key Value Observing.

One way to make -observeValueForKeyPath:ofObject:change:context: a little bit more elegant is to use key path strings as notification names as follows:

- (void)observeValueForKeyPath:(NSString *)keyPath
   ofObject:(id)object change:(NSDictionary *)changeDictionary
   context:(void *)context
{
   // copy the change dictionary and add the context to it
   NSMutableDictionary  *infoDictionary = [NSMutableDictionary
      dictionaryWithDictionary:changeDictionary];
   [infoDictionary setObject:context forKey:@"MYBindingContext"];

   // post a notification to interested observers using the key path as
   // the notification name
   [[NSNotificationCenter defaultCenter] postNotificationName:keyPath
      object:object userInfo:infoDictionary];

   // be sure to call the super implementation
   [super observeValueForKeyPath:keyPath
      ofObject:object change:change
      context:context];
}

If you use the approach of converting Key Value Observation notifications into NSNotifications, you can have any number of observers that each register a different selector for the same key path. Unfortunately, the NSNotification approach has problems of its own. Using key path strings as notification names is not ideal because key paths are specified in Interface Builder and must be duplicated exactly in your code that registers for notifications. A simple change in Interface Builder could necessitate changes to notification code in multiple disparate places within your application. The compiler can't detect errors in the key path strings, so you must test at runtime to detect key path errors. Nevertheless, NSNotificationCenter provides at least one way to circumvent the use of explicit string comparisons in your own code.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020