Re: [Pyobjc-dev] Debugging pyobjc crash?
Brought to you by:
ronaldoussoren
From: Han-Wen N. <ha...@xs...> - 2005-06-24 12:20:34
|
Ronald Oussoren wrote: >>> It could be a missing type annotation somewhere in your code. The >>> traceback indicates that PyObjC is trying to send a message to >>> something that's not a valid object. The most likely reason for >>> that is a bad or missing type annotation somewhere. In your case >>> that would be a bad outlet definition, which is really odd. >>> >> >> how could an outlet definition be "bad" ? > > > Do you have explicit objc.ivar or objc.IBOutlet definitions in your > classes? The traceback seems to indicate that you have an objc.ivar of > type '@' (object) where the Objective-C code thinks it is another type. not that I can recall. > Now that I've written this down I'm pretty sure that this isn't what's > happening. It is more likely that one of your outlets points to garbage > (and object that was released). >> yes. > > > Is there source-code for that somewhere? I've downloaded the sourcecode > on the download page and that doesn't seem to contain the Cocoa GUI. > http://savannah.gnu.org/cgi-bin/viewcvs/lilypond/installers/macos/ the GUI itself is in LilyPad/ . The complete bundle is built by buildmac.py - but I've never tried building it on a clean machine yet, and building is somewhat involved. -- Han-Wen Nienhuys - ha...@xs... - http://www.xs4all.nl/~hanwen |