Hmmm ... whatever point you're trying to make is sailing right
over my head. ;-)
Sorry, it wasn't clear from your description why it was necessary for
a managed object to be able to determine with what document it is
associated.
It does make me think, though - should the Keyword class itself do
all the work here, rather than ask the document to do it? That
*should* negate the need to talk directly with the document itself
altogether. Is that the right direction?
Yes. As a controller, it's aware of when modifications are being
made and is able to coordinate responses to changes. It's not up to
the Keyword to act as a controller in that way.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/email@hidden
