Re: master-detail: binding array controller to the attribute of selection of master array controller
Re: master-detail: binding array controller to the attribute of selection of master array controller
- Subject: Re: master-detail: binding array controller to the attribute of selection of master array controller
- From: Izidor Jerebic <email@hidden>
- Date: Wed, 23 Jul 2008 20:51:00 +0200
On 23.7.2008, at 20:08, mmalc crawford wrote:
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.
Hm, the docs say:
Typically, the content binding is created automatically when the
initial NSTableColumn binding is made, binding to the column's
NSArrayController.
I don't see what is inappropriate.
It should work, because I set it to the same array controller that the
bindings machinery would set it anyway, right? And binding machinery
would override it anyway, right? It says nothing about "do not set
this binding because selection notifications won't work". It says that
it is read-only, but why is there any effect when setting it in
InterfaceBuilder? And why am I allowed to set it? What does it mean
'read-only' ?
But all this is besides the point.
This is my point:
I made the mistake - I never intended to create this binding. And
computer did not help me in preventing nor finding my mistake. There
should be a mechanism to help me. If there was framework source code
access, it would help me find my mistake. If there were debugging
framework logs with sufficient info, it would help me find my mistake.
Interface Builder could even prevent me making this mistake. It is the
bindings author's duty to provide helping mechanisms, because we all
make mistakes (and bindings probably have bugs, too). This user-
unfriendly attitude is the point.
I was asking whether there are any help mechanisms for bindings that
I am unaware of. Only documentation and advice "don't make mistakes"
is not enough, imho. There's too much magic...
izidor
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden