Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!tut.cis.ohio-state.edu!cwjcc!gatech!unmvax!unmvax.cs.unm.edu!stone
From: stone@unmvax.cs.unm.edu (Andrew Stone)
Newsgroups: comp.sys.next
Subject: Re: 0.9 Interface Builder vs. Application Kit
Summary: using NXAttachPopUpList
Keywords: pop
Message-ID: <177@unmvax.unm.edu>
Date: 25 Jun 89 23:20:45 GMT
References: <130003@gore.com>
Sender: news@unmvax.unm.edu
Reply-To: stone@unmvax.cs.unm.edu (Andrew Stone)
Organization: University of New Mexico at Albuquerque
Lines: 35

In article <130003@gore.com> jacob@gore.com (Jacob Gore) writes:
>There are discrepancies between the Application Kit documentation and what
>can be accessed through the Interface Builder.  For example, the class
>browser does not show PopUpList at all, while the manual shows it as a
>subclass of Menu.  Can PopUpLists be used in the IB?

You can sort of use IB to create pop up lists.
I create a regular button as a temporary stand in, and 
set its target/action to a subclass I've written, and an
appropriate method. Create an outlet in this class and connect
it to the stand-in button. If the outlet is named "fontPopUp",
then IB creates a method -setFontPopUp:anObject which you
enhance like this:

- setFontPopUp:anObject
{   
    int i;
    FontPopUp = anObject;
    
    fontPopUpList = [PopUpList new];
    for (i=0;i<NUMFONTS;i++) [fontPopUpList addItem:FONTS[i]];
    NXAttachPopUpList(anObject,fontPopUpList);

    return self;
}

Basically, you build a list with the titles of your pop up items, 
and then connect it to the button with NXAttachPopUpList.

andrew

||<<++>>||<<-->>||<<==>>||<<++>>||<<??>>||<<++>>||<<-->>||<<==>>||<<++>>||
!!	   Andrew Stone	            !!        the fictive milieu of	!!
!!         stone@hydra.unm.edu	    <> 	      contemporary society!	!!
||<<++>>||<<-->>||<<==>>||<<++>>||<<??>>||<<++>>||<<-->>||<<==>>||<<++>>||