On Jun 11, 2009, at 07:43, Mac First wrote:
I can change things around to do them in a different order and get
the error to come out for key 'KEY' instead of 'IMAGE', but it's
basically the same problem. If I break on the code and examine my
array (the referencedObject), it's an array of dictionaries, with
keys KEY and IMAGE, as expected, long before the view displays.
Am I missing some best-practices thing, here? Is there a special
ordering in which I need to do this stuff? I swear this worked a
week ago and I didn't change anything (other than to install the new
SDK <sigh>)
I haven't tried to use NSCollectionView since, maybe, 10.5.4, but it
used to be horribly flawed and may still be.
The problem (I thought, though it was never confirmed) was that
bindings from the subview prototype are of course not the actual
bindings to use -- NSCollectionView has to arrange for the *actual*
subviews to have bindings patterned on the ones in the prototype. At
the time, NSCollectionView didn't seem to be doing this properly, and
the way it failed depended on the order of the objects in the nib
file, so that simply editing your xib file would cause it to fail in
different ways.
Now I may be maligning NSCollectionView, but my conclusion at the time
(based on this and the class's other faults, and its truly
unenlightening documentation) that NSCollectionView is a class to be
avoided.
FWIW
_______________________________________________
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 arch...@mail-archive.com
