• 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: Is willChangeValueForKey: always needed?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Is willChangeValueForKey: always needed?


  • Subject: Re: Is willChangeValueForKey: always needed?
  • From: Chris Hanson <email@hidden>
  • Date: Thu, 16 Nov 2006 23:48:40 -0800

On Nov 16, 2006, at 10:11 PM, Chris Hanson wrote:

On Nov 16, 2006, at 4:22 PM, David Catmull wrote:

I have a case where the value in question is calculated based on other values (which tab is selected, and whether a certain text field has text), and the key is simply the name of the method that calculates the value. So when one of those other values changes, it's too late to say that the calculated value "will" change.

You should make this key's value on the values of the other keys.

I intended to write:

You should make this key's value dependent on the values of the other keys.

Sorry for any confusion!

  -- Chris

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >Is willChangeValueForKey: always needed? (From: David Catmull <email@hidden>)
 >Re: Is willChangeValueForKey: always needed? (From: Chris Hanson <email@hidden>)

  • Prev by Date: Re: CFRunLookFindMode crash
  • Next by Date: Re: More NSDictionary to CFDictionary
  • Previous by thread: Re: Is willChangeValueForKey: always needed?
  • Next by thread: Re: Is willChangeValueForKey: always needed?
  • Index(es):
    • Date
    • Thread