Thread: [Pyobjc-dev] Problem with auxiliary windows
Brought to you by:
ronaldoussoren
From: Robert B. <br...@uc...> - 2004-09-13 20:18:00
|
I have a program that consists of a main window and an auxiliary window which can be opened by clicking a button on the main window. I'm programmatically loading the nib file for the aux window, creating a controller for it and displaying it (ie not linking the two through Interface Builder). Everything works fine in the version written entirely in Objective-C. However, the PyObjC version (as nearly as possible a direct translation) will display the aux window but crashes when the aux window is given the focus. The backtrace looks like there's an access of address 0 when an event is sent to the window. Do I have to register the new window with the windowing system somehow? --------------------------------------------------- Robb Brown Seaman Family MR Research Centre Calgary, Alberta, Canada |
From: Ronald O. <ron...@ma...> - 2004-09-14 05:26:10
|
On 13-sep-04, at 22:17, Robert Brown wrote: > I have a program that consists of a main window and an auxiliary > window which can be opened by clicking a button on the main window. > I'm programmatically loading the nib file for the aux window, creating > a controller for it and displaying it (ie not linking the two through > Interface Builder). > > Everything works fine in the version written entirely in Objective-C. > However, the PyObjC version (as nearly as possible a direct > translation) will display the aux window but crashes when the aux > window is given the focus. The backtrace looks like there's an access > of address 0 when an event is sent to the window. > > Do I have to register the new window with the windowing system somehow? You don't. There's probably something wrong with the translation from Objective-C. Could you create a minimal example that also crashes? Ronald |
From: Robert B. <br...@uc...> - 2004-09-15 19:39:33
|
Thanks for the reply and offer to look at the code... I found the problem while building the minimum example. I had an unconnected outlet in the auxiliary window's controller object that was supposed to be the NSWindowController. I was setting this variable with Python to be a new NSWindowController. Something didn't like that. Using a purely Python instance variable to hold the window controller works perfectly. I suppose there's something special about an outlet so that I can't just set it using a Python myoutlet = someclass.alloc().init() call? On 13-Sep-04, at 11:25 PM, Ronald Oussoren wrote: > > On 13-sep-04, at 22:17, Robert Brown wrote: > >> I have a program that consists of a main window and an auxiliary >> window which can be opened by clicking a button on the main window. >> I'm programmatically loading the nib file for the aux window, >> creating a controller for it and displaying it (ie not linking the >> two through Interface Builder). >> >> Everything works fine in the version written entirely in Objective-C. >> However, the PyObjC version (as nearly as possible a direct >> translation) will display the aux window but crashes when the aux >> window is given the focus. The backtrace looks like there's an >> access of address 0 when an event is sent to the window. >> >> Do I have to register the new window with the windowing system >> somehow? > > You don't. There's probably something wrong with the translation from > Objective-C. Could you create a minimal example that also crashes? > > Ronald > > > > ------------------------------------------------------- > This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170 > Project Admins to receive an Apple iPod Mini FREE for your judgement on > who ports your project to Linux PPC the best. Sponsored by IBM. > Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php > _______________________________________________ > Pyobjc-dev mailing list > Pyo...@li... > https://lists.sourceforge.net/lists/listinfo/pyobjc-dev > --------------------------------------------------- Robb Brown Seaman Family MR Research Centre Calgary, Alberta, Canada |