I pulled my hair out over this one, but I finally found an acceptable workaround, although it doesn't solve the fundamental problem of NSDictionaryController.
Thanks very much for the reply and workaround. I will explore this solution further.
The NSDictionaryController/bindings route seems to work fine if you have a simple mutable dictionary in which the keys are strings and the values are discrete objects like NSStrings or NSNumbers. Then you can edit the values with no problem. It just seems to get difficult when the dictionary values are themselves collections. I could live with this I suppose, in cases where read-only display of the dictionary was the primary goal. However it would really be nice to be able to edit the contents of collections, and the present limitations should really be mentioned in the documentation (maybe the current docs say so in some obtuse way, but if so I didn't catch it).
Thanks again, Rick _______________________________________________ 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
