MInefield bindings in Xcode and Interface Builder

Question

Well, having worked on Cocoa Dev Central's Tutorial “Creating a Basic Data Application”, I started experimenting with creating my own application, using the code and .nibfile from the tutorial as a link to make sure everything is correctly composed. All in all, I did a good job of this, but it seems like I am trapped.

I create a form with two blocks NSTextView, as in the tutorial, but associated with different attributes inside the same object. All other controls work correctly and save / update their values ​​when I go between records (minus some kind of stupid date when the second box does not want to save their values). I checked all the snap settings and NSArrayControlleron .nibfrom the tutorial to see where things can be disabled; which led to disabling the first text field and then reconnecting it with the same settings, and it unexpectedly magically worked. The second block does not want to behave, however, and continues to break the program (a debugger appears, listing all kinds of variables and memory addresses, etc., which frankly goes beyond my understanding).

Currently, the offending unit is configured as follows:

Class: NSTextView
Value: Bound to `history`
    Controller Key: selection
    Model Key Path: `description`
    Checked: Allows Editing Multiple Values Selection
    Checked: Conditionally Sets Editable
    Checked: Raises For Not Applicable Keys

Any insight on what's going on here?

Answer 1

Ok, got it. The name of the attribute changed from description, and it began to behave; It seems that the name was causing something when it compiled, that the initial error was skipped.