Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!ucbvax!agate!eos!shelby!polya!ali
From: ali@polya.Stanford.EDU (Ali T. Ozer)
Newsgroups: comp.sys.next
Subject: Re: 0.9 Interface Builder vs. Application Kit
Message-ID: <10255@polya.Stanford.EDU>
Date: 26 Jun 89 06:32:30 GMT
References: <130003@gore.com>
Sender: Ali T. Ozer <ali@polya.Stanford.EDU>
Reply-To: aozer@NeXT.com (Ali Ozer)
Distribution: na
Organization: .
Lines: 22

In article <130003@gore.com> jacob@gore.com (Jacob Gore) writes:
>Can PopUpLists be used in the IB?

Not directly; the best way to use PopUpLists through IB is to create
a button and use NXAttachPopUpList() at runtime (a good way to do this
might be to make the button an outlet of something and attach the
PopUpList in the setOutletName: method).

>ScrollView is documented as a general scrolling view, with optional
>vertical and horizontal sliders and with any content view possible.  The IB
>has on its Views palette an icon that looks like it's for scrolling text,
>and the default instance variable name for it is ScrollingText, but the
>Inspector window says "ScrollView Inspector", even though the Attributes
>subpanel talks about text attributes.  Is ScrollingText a subclass of
>ScrollView? 

No, it's simply a ScrollView whose docView is set to an instance of the Text
class. IB doesn't yet provide the means to create a ScrollView whose
docView is an arbitrary view.

Ali Ozer, NeXT Developer Support
aozer@NeXT.com