How do I make this code KVO compliant?

Question

I'm trying to get a grip on bindings and have set up a CPWindow with a CPTextView in xcode and bound the window and the textview to their respective outlets.

I'm getting a bit stuck however trying to make the textview display the _xmlContent. I've set the binding in xcode to "delegate" and the key path to xmlContent (also tried self.xmlContent and _xmlContent and all variations thereof that I could think of).

    @import <Foundation/Foundation.j>
    @import <AppKit/AppKit.j>

    @implementation AppController : CPObject
    {
        @outlet CPWindow    theWindow;
        @outlet CPTextView  codeView;

        CPString _xmlContent @accessors(property=xmlContent);
    }

    // ...

    @end

The message I'm getting now is:

CPUndefinedKeyException: <AppController 0x00a177> is not key value coding-compliant for the key xmlContent

How do I make my AppController key value coding compliant for the key "xmlContent"?

score 1 · Accepted Answer · answered Dec 14 '16 at 18:44

1

Your code looks correct. I recreated it myself and it works fine for me:

@implementation AppController : CPObject
{
    @outlet CPWindow    theWindow;

    CPString _xmlContent @accessors(property=xmlContent);
}

- (void)applicationDidFinishLaunching:(CPNotification)aNotification
{
}

- (void)awakeFromCib
{
    [theWindow setFullPlatformWindow:YES];
    [self setXmlContent:@"kitten"];

You should verify that you are running the code you think you are running. One common pitfall here is that some web-browsers really like to hang on to cached copies of your code so make sure you have the "Disable Caches" option enabled in whatever browser you are testing with.

If all else fails, change the port number of your development HTTP server and load the page from the new URL. This will force the browser to get fresh copies of everything (because the URL changed).

answered Dec 14 '16 at 18:44

Alexander Ljungberg

6,302
4
31
37

While I did not have "Disable caches" enabled in Safari (do now!), i did try several tricks to force cache busting. I thought I even manually cleared all caches in Safari.but I guess I was wrong. – Kris Dec 14 '16 at 19:29
Yeah Safari can be incredibly clingy to its cache. Chrome has its own set of problems, but I have found that the "disable cache while developer tools are open" option to work quite well while developing. – Alexander Ljungberg Dec 14 '16 at 19:40
That will be my new strategy :) – Kris Dec 14 '16 at 21:24

How do I make this code KVO compliant?

1 Answers1