Comments on: PyAverager tutorial error with Cocoa Bindings http://patternbuffer.wordpress.com/2008/05/05/pyaverager-tutorial-error-with-cocoa-bindings/ Kyle Crawford Fri, 06 Nov 2009 02:53:19 +0000 http://wordpress.com/ hourly 1 By: Kyle Crawford http://patternbuffer.wordpress.com/2008/05/05/pyaverager-tutorial-error-with-cocoa-bindings/#comment-133 Kyle Crawford Wed, 29 Oct 2008 01:13:44 +0000 http://patternbuffer.wordpress.com/?p=38#comment-133 It is in the same folder as PyAverager.xcodeproj. It is part of the project and shows in the Groups & Files section when you have it open in Xcode. It is in the same folder as PyAverager.xcodeproj. It is part of the project and shows in the Groups & Files section when you have it open in Xcode.

]]> By: Rasmus Tausen http://patternbuffer.wordpress.com/2008/05/05/pyaverager-tutorial-error-with-cocoa-bindings/#comment-132 Rasmus Tausen Tue, 28 Oct 2008 20:01:16 +0000 http://patternbuffer.wordpress.com/?p=38#comment-132 Dear Kyle Crawford Where do I find a file named "main.py" - sorry I don't get it... Dear Kyle Crawford

Where do I find a file named “main.py” – sorry I don’t get it…

]]> By: kourge http://patternbuffer.wordpress.com/2008/05/05/pyaverager-tutorial-error-with-cocoa-bindings/#comment-78 kourge Sun, 25 May 2008 17:33:05 +0000 http://patternbuffer.wordpress.com/?p=38#comment-78 This is a real lifesaver. I was worried when I found Tiger references in the tutorial (because that indicates the tutorial is quite outdated) given that I'm on Leopard, even though Leopard ships with PyObjC by default. Everything seemed fine until it seems that binding doesn't work in IB. After wondering what could have gone wrong for a whole day, I then found this post. This really is the same kind of idiocracy in the RubyCocoa tutorial, where it told the reader to add a Custom View (barebone NSView) in IB, then set its identity to IKImageBrowserView, when in fact the IKImageBrowserView is available in the Library panel. Even after this, it told the reader not to worry because even though IKImageBrowserView belongs to Quartz.framework and its not added to the project, AppKit.framework is dependent on Quartz.framework. Which was wrong again, because it would throw an NSInvalidUnarchiveOperationException, saying that it "cannot decode object of class". So the solution was to manually add Quartz.framework to the project. This is a real lifesaver. I was worried when I found Tiger references in the tutorial (because that indicates the tutorial is quite outdated) given that I’m on Leopard, even though Leopard ships with PyObjC by default.
Everything seemed fine until it seems that binding doesn’t work in IB. After wondering what could have gone wrong for a whole day, I then found this post.
This really is the same kind of idiocracy in the RubyCocoa tutorial, where it told the reader to add a Custom View (barebone NSView) in IB, then set its identity to IKImageBrowserView, when in fact the IKImageBrowserView is available in the Library panel. Even after this, it told the reader not to worry because even though IKImageBrowserView belongs to Quartz.framework and its not added to the project, AppKit.framework is dependent on Quartz.framework. Which was wrong again, because it would throw an NSInvalidUnarchiveOperationException, saying that it “cannot decode object of class”. So the solution was to manually add Quartz.framework to the project.

]]>