Sparkle

Bindings aren't working

Asked by LegosJedi

Okay, I'm having trouble binding Sparkle to my preferences window for my app. I'm pretty sure I've got everything hooked up right, but it just refuses to work; both the checkbox and the pop-up box are disabled. Here's my console log for that part:

2008-12-27 09:57:58.383 FireTunes[1806:10b] Cocoa Bindings: Error accessing value for key path automaticallyChecksForUpdates of object <SUUpdater: 0x150910> (from bound object <NSButton: 0x59278a0> with object ID 6 in Nib named PrefsWindow.nib): [<SUUpdater 0x150910> valueForUndefinedKey:]: this class is not key value coding-compliant for the key automaticallyChecksForUpdates.

2008-12-27 09:57:58.385 FireTunes[1806:10b] Cocoa Bindings: Error accessing value for key path updateCheckInterval of object <SUUpdater: 0x150910> (from bound object <NSPopUpButton: 0x5928ae0> with object ID 133 in Nib named PrefsWindow.nib): [<SUUpdater 0x150910> valueForUndefinedKey:]: this class is not key value coding-compliant for the key updateCheckInterval.

I've done a google search, and it's told me that my bindings are messed up, pretty much, but, I'm not quite sure how to fix them, cause, well, bindings are still somewhat new to me.

Any help?

Question information

Language:
English Edit question
Status:
Answered
For:
Sparkle Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
LegosJedi (legos-jedi) said : 		#1

Oh, forgot to mention this: This is with Xcode 3.1.

Revision history for this message
Andy Matuschak (andymatuschak) said : 		#2

That's really odd, since SUUpdater is definitely KVC-compliant for automaticallyChecksForUpdates. The only possibility I can think of is that maybe you have an older version of Sparkle? Take a look at your SUUpdater.h—are those keys in there?

Revision history for this message
LegosJedi (legos-jedi) said : 		#3

I was using the 1.5 4th Beta, but now that I see that Beta 6 is out, I'll give that one a go and report back.

Revision history for this message
Hofman (cmhofman) said : 		#4

This almost certainly explains this problem, as these keys were introduced in 1.5b5.

Can you help with this problem?

Provide an answer of your own, or ask LegosJedi for more information if necessary.

To post a message you must log in.