On Jun 30, 2008, at 2:53 PM, Hamish Allan wrote:
On Mon, Jun 30, 2008 at 10:43 PM, Ron Lue-Sang <[EMAIL PROTECTED]>
wrote:
Yes! infoForBinding is what you should use to implement the logic
in #1.
[...]
2b) Implement the "read" logic yourself by implementing bind:.
What puzzles me is that NSTextField doesn't seem to do either of
these, yet still seems to know which key path to update after user
interaction.
Hamish
Yep, that's right. The bindings machinery uses a faster cache. The
same way as bindable-view implementors are free to cache the binding
information any way you like. You don't need to use infoForBinding,
but it's the easiest solution to describe.
--------------------------
RONZILLA
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
