• 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: KVO and the observeValueForKeyPath bottleneck
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: KVO and the observeValueForKeyPath bottleneck


  • Subject: Re: KVO and the observeValueForKeyPath bottleneck
  • From: Scott Anguish <email@hidden>
  • Date: Thu, 20 Jul 2006 16:14:51 -0400


On Jul 20, 2006, at 3:25 PM, George Orthwein wrote:

I don't think implementing "one way" or "read only" bindings is a misuse, though it almost seems that way since there aren't any examples or mentions of it in the docs that I remember seeing. I think I'll file a doc request.

binding between model objects isn't recommended at all. the bindings doc is clear about how we recommend doing it (controller to model, view to controller.. it would be useful to extend that to the occasional view to model as well though, I'll add it to the list). We don't say how we don't recommend doing it in general though..


It does seem to be a sly way of avoiding the observeValueForKeyPath bottleneck though.

_______________________________________________ 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: 
 >Re: KVO and the observeValueForKeyPath bottleneck (From: Matt Neuburg <email@hidden>)
 >Re: KVO and the observeValueForKeyPath bottleneck (From: George Orthwein <email@hidden>)

  • Prev by Date: Re: Creating a new implementation of NSPersistantStoreCoordinator to use a different backend?
  • Next by Date: menu:updateItem:atIndex:shouldCancel: Crazy instead of Lazy!
  • Previous by thread: Re: KVO and the observeValueForKeyPath bottleneck
  • Next by thread: Re: KVO and the observeValueForKeyPath bottleneck
  • Index(es):
    • Date
    • Thread