Re: Core Data and @count keypath
Re: Core Data and @count keypath
- Subject: Re: Core Data and @count keypath
- From: Scott Anguish <email@hidden>
- Date: Thu, 9 Feb 2006 04:29:59 -0500
On Feb 8, 2006, at 7:19 PM, John R. Timmer wrote:
Aside from binding to a display pattern, how does one create a read-
only binding (or was that it)?
the system has several bindings that are read-only. Changes you
make to the model properties are reflected in the view. I'm not sure
that you can provide a 'read-only' marking for your own view bindings
at this point. You can implement the binding for a view in such a
way that it acts as if it is read only (that is, ensure that it never
attempts to write a changed value back to that binding -- or disable
it from editing completely)
probably best to file a bug that requests more explicit ways of
specifying binding behaviors like read-only, attributes available, etc..
On Feb 8, 2006, at 11:15 AM, Chris Hanson wrote:
On Feb 7, 2006, at 4:30 AM, John R. Timmer wrote:
You have to bind to a value that's read/write. @count is read
only. If you need to bind to it, make a managed object key like
arrayCount that returns the count in the getter method, and does
nothing in the setter method.
You should not need to do this; binding a label or other non-
editable value to a read-only key should work just fine. See the
bindings generated for a multiple-instance interface created by
option-dragging a Core Data entity from a model to a window in
Interface Builder.
_______________________________________________
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