home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.next.programmer
- Path: sparky!uunet!darwin.sura.net!jvnc.net!princeton!phoenix.Princeton.EDU!sksircar
- From: ssircar@canon.com (Subrata Sircar)
- Subject: Re: how do outlets work?
- Message-ID: <1992Jul29.224508.1660@Princeton.EDU>
- Originator: news@ernie.Princeton.EDU
- Sender: ssircar@canon.com
- Nntp-Posting-Host: phoenix.princeton.edu
- Reply-To: ssircar@canon.com (Subrata Sircar)
- Organization: SPAMIT
- References: <1992Jul29.163410.23660@steggie.uucp> <1992Jul29.191912.206@digifix!uunet.ca>
- Distribution: usa
- Date: Wed, 29 Jul 1992 22:45:08 GMT
- Lines: 30
-
- >Eric Fronberg writes
- >> This may be a naive question. I'm confused about the workings of
- >> outlets in interface builder. I understand what outlets are supposed
- >> to do -- provide access to instances of other objects, but I'm
- >> confused how Interface Builder accomplishes this.
-
- Interface Builder actually does something like the following:
-
- if ([yourObject respondsTo:@selector(setTheOutlet:)])
- [yourObject setTheOutlet:outletID];
-
- Those methods used to be automatically generated by IB, but are not anymore.
- If you include them, you can do a lot of neat things in those methods. They
- are particularly useful with FormCells, where you can set the input format
- and so forth.
-
- sanguish@digifix.com writes:
- > Is this still supported? I can't find it anywhere in the current
- >documentation.
-
- It is still supported. As far as the future goes, your guess is as good as
- mine.
-
-
-
- --
- Subrata Sircar | ssircar@canon.com | Prophet & SPAMIT Charter Member
- Canon Information Systems and I do not speak for each other on all things.
- "I wish people wouldn't instantly assume that I am an idiot." (Valentine)
- "A restaurant is a whorehouse that does food instead of sex." (Roger Lustig)
-