Aha!
I did have custom accessors (I'd actually forgotten about them, I've
let this sit too long...), but when comparing against that
documentation I found the problem.
My notifications (didChange/etc.) were sent for the primitive values
instead of using the straight names -- "primitiveSo
On Aug 18, 2010, at 18:00, Frank D. Engel, Jr. wrote:
> I have a controller class which is represented as a simple object (cube icon)
> in Interface Builder. This class has an "id" field to which I assign various
> instances of core data entities (represented by a subclass of NSManagedObject
>
Is it just a case of making your controls continuous, or setting your bindings
to continuously update values?
On 19/08/2010, at 11:00 AM, Frank D. Engel, Jr. wrote:
> Then the "value" bindings of the NSSlider and NSCheckbox are both
> "selectedWhatever.someField".
>
>
> The problem I am havin
Hi,
Hoping this is something simple that I'm missing...
I have a controller class which is represented as a simple object
(cube icon) in Interface Builder. This class has an "id" field to
which I assign various instances of core data entities (represented by
a subclass of NSManagedObject
The popup button has:
Content bound to MyArrayController.arrangedObjects
Content Values bound to MyArrayController.arrangedObjects.name
Sometimes, and is vaguely seems to be related to changing the XIB,
the labels of the cells in the popup are what I would expect from
calling -description on
Hi,
Precis: I'm sometimes seeing what appears to be the result of
[(NSManagedObject) description] in an NSPopUpButton instead of the
expected value as set in bindings.
I've got a Core Data Document Based Application in which I'm seeing
occasional issues with a binding.
The application u
