Re: Problem with NSObjectController key path
Re: Problem with NSObjectController key path
- Subject: Re: Problem with NSObjectController key path
- From: mmalcolm crawford <email@hidden>
- Date: Sat, 16 Apr 2005 00:38:37 -0700
On Apr 16, 2005, at 12:07 AM, sravan wrote:
Can we have our own controller key in the key path of the
NSObjectController(eg selection), key path like employee.name
instead of selection.name.
If I understand correctly what you mean, then in theory yes (you can
write code to support it) but in practice you're working against the
system...
This will be useful for me to maintain two different type of
objects like employee, department and i will specify key paths
like employee.name and department.name for TextFields and they
should show the names of the current employee and department
object's name values.
... I would suggest instead using two object controllers -- one to
represent the employee, the other the department.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden