On 29 Mar 2008, at 06:29, Ron Lue-Sang wrote:
There's also the controller attribute "Always Use Multi Value
Marker" which will keep the controller from even looking at the
property values of the selected objects as long as more than one
object is selected in the controller.
Of course, this won't help if your textfield is editable and bound
to the controller's selection.foo keypath and the user tries to edit
the value.
Well, as said, in many cases I really need the compound value, in the
likely case that the property is the same for the whole selection.
However, for a complete library the compound value is useless. So I
might have to tweak this Multiple Value behavior.
The user will rarely have to edit values, it is mostly (though not
strictly) a consulting UI. If he does, it is no more than once per
object/property. In that case, I can take the overhead if necessary.
_______________________________________________
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]
