On 23.7.2008, at 23:42, mmalc crawford wrote:
On Jul 23, 2008, at 11:51 AM, Izidor Jerebic wrote:
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?
No, you didn't. You only set the 'content' binding'.
And binding machinery would override it anyway, right?
Wrong.
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' ?
You are allowed to set it. If you set it, though, you also have to
set the 'sortDescriptors' and 'selectionIndexes' bindings as well --
Thank you for the explanations. I see now why it didn't work.
izidor
P.S. But I would still like some other bindings debug mechanism then
'send email to cocoa-dev', though it turned out great in my case :-)
_______________________________________________
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]
