home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ogicse!henson!news.u.washington.edu!hardy.u.washington.edu!zeno
- From: zeno@hardy.u.washington.edu (Sean T. Lamont)
- Newsgroups: comp.sys.next.programmer
- Subject: Re: Why doesn't initFrame see Forms, make assignments?
- Message-ID: <1992Jul22.050144.14366@u.washington.edu>
- Date: 22 Jul 92 05:01:44 GMT
- Article-I.D.: u.1992Jul22.050144.14366
- References: <1992Jul21.234601.8528@u.washington.edu>
- Sender: news@u.washington.edu (USENET News System)
- Organization: Abstract Software
- Lines: 21
-
- In article <1992Jul21.234601.8528@u.washington.edu> goldly@u.washington.edu (Lloyd P. Goldwasser) writes:
- >Why doesn't - initFrame see outlets that the rest of its object sees, such
- >as Forms?
-
- If you're using an IB-generated view, at the point when -initFrame is called
- within the view the form isn't necessarily instantiated yet. if you use
- an NXApp delegate you can get at the object after everything has been
- instantiated by using the "-appDidInit:sender" delegate method.
-
- you might want to use gsb to check at the point you're trying to manipulate
- the form and see if it has any value. If it's not instantiated, it will have
- no value and any messages sent to it get lost in the ether.
-
-
-
-
- --
- Sean T. Lamont, Abstract Software | "Don't oppress me, It's
- zeno@u.washington.edu | 'computer of color!' "
- Next Mail............................... | yang.cpac.washington.edu!zebu!zeno
- ----------------"My employers opinions are my own, not yours."-----------------
-