• 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: recursing bindings?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: recursing bindings?


  • Subject: Re: recursing bindings?
  • From: Joshua Scott Emmons <email@hidden>
  • Date: Thu, 16 Jun 2005 18:33:40 -0400

How do I update the observable object I'm bound to without causing it to immediately send me an observeValueForKeyPath... with the value I just sent it?

Umm, don't send the update in your setValue: method?

Fair enough. But I was under the impression that half the point of bindings is that the the values are updated in both directions. If objectA.foo is bound to the property bar in objectB, then when foo is updated, bar gets the value AND when bar is updated, that gets propagated to foo.


That seems to be the way it works with the stock views like NSTextView, etc. Are you saying that, the reason these views work this way is because they send out the notification in some updateForEvent method instead of in the accessor itself?

Cheers,
-jse
_______________________________________________
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


  • Follow-Ups:
    • Re: recursing bindings?
      • From: mmalcolm crawford <email@hidden>
References: 
 >recursing bindings? (From: Joshua Scott Emmons <email@hidden>)
 >Re: recursing bindings? (From: mmalcolm crawford <email@hidden>)

  • Prev by Date: Letters cut-off in NSOutlineview?
  • Next by Date: QT & Cocoa
  • Previous by thread: Re: recursing bindings?
  • Next by thread: Re: recursing bindings?
  • Index(es):
    • Date
    • Thread