Path: utzoo!attcan!uunet!dtgcube!ed
From: ed@DTG.COM (Edward Jung)
Newsgroups: comp.sys.next
Subject: Re: window object and awake method
Keywords: window awake
Message-ID: <1989Dec3.185249.5197@uunet!dtgcube>
Date: 3 Dec 89 18:52:49 GMT
References: <128@kgw2.UUCP>
Sender: ed@uunet!dtgcube (Edward Jung)
Reply-To: ed@DTG.COM (Edward Jung)
Organization: The Deep Thought Group, L.P.
Lines: 28
In-Reply-To: dennisg@kgw2.UUCP (Dennis Glatting)

In article <128@kgw2.UUCP>, dennisg@kgw2 (Dennis Glatting) writes:
>
>i've got a problem.
>i've created a subclass of a window which i built with IB.
>my awake method in this subclass never gets called nor does
>its finishUnarchiving method.  what's wrong?
>

When Interface Builder creates your classes, it is not "unarchiving"
them.  Archiving and archiving is performed by the read:/write: method
pair.  Interface Builder creates objects through the run-time system,
thereby making the process essentially language independent (recall
that the only language dependent parts of Interface Builder are the
parse and unparse operations).

If you want to change the behavior of the window, use the
newContent:... factory method instead (see docs or header files for
the Window class).

If you want to do something after everything is set up, you could try
working with the key and main related window methods (e.g. via a
delegate, or override orderFront:/orderWindow:relativeTo:, you get the
idea.).
-- 
Edward Jung                             The Deep Thought Group, L.P.
BIX: ejung                                      3400 Swede Hill Road
NeXT or UNIX mail                                Clinton, WA.  98236
        UUCP: uunet!dtgcube!ed          Internet: ed@dtg.com