pyobjc-dev

[Pyobjc-dev] How to get NSDoc subclass's window outlet?

[David E. <epp...@ic...>]

I have a Python subclass of NSDocument, that wants to access the 
NSDocument's window outlet.  Is it possible?  If I do window = 
objc.IBOutlet("window"), I get None as the value of the outlet (despite it 
being connected in the nib, and other outlets working).  But if I don't set 
the outlet in the Python code, I get exception: No attribute window.  I 
can't see an accessor function that would give me the same information in 
the NSDocument documentation.

Obvious workaround: make a redundant outlet with another name...so this 
isn't urgent, but I would eventually like to know.
--
David Eppstein       UC Irvine Dept. of Information & Computer Science
epp...@ic... http://www.ics.uci.edu/~eppstein/

Re: [Pyobjc-dev] How to get NSDoc subclass's window outlet?

[<bb...@ma...>]

On Sunday, Dec 15, 2002, at 02:18 US/Eastern, David Eppstein wrote:
> I have a Python subclass of NSDocument, that wants to access the 
> NSDocument's window outlet.  Is it possible?  If I do window = 
> objc.IBOutlet("window"), I get None as the value of the outlet 
> (despite it being connected in the nib, and other outlets working).  
> But if I don't set the outlet in the Python code, I get exception: No 
> attribute window.  I can't see an accessor function that would give me 
> the same information in the NSDocument documentation.

Generally, you never should or need to access an instance variable of 
AppKit classes directly, even when subclassing.  An accessor method is 
almost always provided.

In this case, NSDocument implements the -window method for exactly this 
purpose.

Try self.window().

If that doesn't work, then there is a bug.

In the case of NSDocument, the iVar is named _window.   Because of the 
way documents manage their windows-- typically through instances of 
NSWindowController, but not always-- the -window method has a bunch of 
additional intelligence to deal with complex situations.

b.bum

Re: [Pyobjc-dev] How to get NSDoc subclass's window outlet?

[David E. <epp...@ic...>]

On 12/15/02 9:32 AM -0500 bb...@ma... wrote:
> Generally, you never should or need to access an instance variable of
> AppKit classes directly, even when subclassing.  An accessor method is
> almost always provided.
>
> In this case, NSDocument implements the -window method for exactly this
> purpose.
>
> Try self.window().
>
> If that doesn't work, then there is a bug.

It doesn't work.  exception: No attribute window
window() is also not documented in the AppKit API reference although 
setWindow:() is there (with a note saying don't call it).

self.windowControllers()[0].window() works though.
--
David Eppstein       UC Irvine Dept. of Information & Computer Science
epp...@ic... http://www.ics.uci.edu/~eppstein/

Re: [Pyobjc-dev] How to get NSDoc subclass's window outlet?

[<bb...@ma...>]

Oh!  You are absolutely correct.  I apologize -- I didn't read the docs 
correctly.

It doesn't work because it shouldn't. :-)

> self.windowControllers()[0].window() works though.

Is the correct way to go about it, ugly though it is.

However, if you need direct access to the window, it is likely that 
there is an alternative design pattern that may be a bit more clean.

b.bum

On Sunday, Dec 15, 2002, at 12:41 US/Eastern, David Eppstein wrote:

> On 12/15/02 9:32 AM -0500 bb...@ma... wrote:
>> Generally, you never should or need to access an instance variable of
>> AppKit classes directly, even when subclassing.  An accessor method is
>> almost always provided.
>>
>> In this case, NSDocument implements the -window method for exactly 
>> this
>> purpose.
>>
>> Try self.window().
>>
>> If that doesn't work, then there is a bug.
>
> It doesn't work.  exception: No attribute window
> window() is also not documented in the AppKit API reference although 
> setWindow:() is there (with a note saying don't call it).
>