On Jul 23, 2008, at 9:40 AM, Izidor Jerebic wrote:
But it again confirmed that bindings are not quite what they should
be. This bug should never happen to me or should be resolved in 5
minutes: InterfaceBuilder should prevent illegal combinations or
there should be a debugging option that would show me which binding
step in runtime is failing. This kind of magic which bindings are
doing can only work when one has access to the source code, so
debugging is possible. Currently, if bindings don't work, you can
only click around and hope something turns out. Not satisfactory at
all.
To stop ranting and be constructive, is there a way of debugging
bindings that would uncover this kind of bug?
Yes, reading the documentation:
<http://developer.apple.com/documentation/Cocoa/Reference/CocoaBindingsRef/BindingsText/NSTableView.html
>
It's not an illegal combination. If you set binding values that are
inappropriate, it's your fault.
See also <http://homepage.mac.com/mmalc/CocoaExamples/controllers.html>
mmalc
_______________________________________________
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]
