On OPENSTEP 4.2 Developer, how do you get the return arrow icon to show
up in a button? The "Discovering OPENSTEP: A Developer Tutorial" manual
shows the icon being available through the "images" tab in the Interface
Builder window when you open the .nib file. It doesn't show up in mine.
The second difference that I've noticed is that when I created a new
project, I got a NEXTSTEP_projectname.nib file and a
WINDOWS_projectname.nib file instead of just the projectname.nib file
that is shown in the documentation. Why?
Is there an updated tutorial somewhere that actually shows the 4.2
interface?
And finally, where is the FAQ for this group? I've been lurking for a
while and haven't seen anything. I checked the Peanuts site and
rtfm.mit.edu and couldn't find anything.
The tutorial seems to be written for an older version of OPENSTEP.
Since version 4.2, you shouldn't use the return key as an explicit
keyboard shortcut for a button, because you can select buttons using
the tab key and then use return to activate the selected button.
If you want to use it anyway, you can get the return icon back into
InterfaceBuilder's images tab by using Edit.app, opening
/NextDeveloper/Apps/InterfaceBuilder.app/Resources/images.plist and
adding a line with ",NSReturnSign".
> The second difference that I've noticed is that when I created a new
> project, I got a NEXTSTEP_projectname.nib file and a
> WINDOWS_projectname.nib file instead of just the projectname.nib file
> that is shown in the documentation. Why?
If you want to develop for OS/Mach and OS/NT, you can create
different nib files for both targets to match the style guide
differences between WinNT and OS/Mach. If you only use OPENSTEP/Mach,
just ignore the WINDOWS nib files.
--
Joerg Kollmann NeXTMail welcome
Joerg Kollmann wrote:
>
> nobody (nob...@nowhere.com) wrote:
> > On OPENSTEP 4.2 Developer, how do you get the return arrow icon to show
> > up in a button?
> > ...
>
> The tutorial seems to be written for an older version of OPENSTEP.
> Since version 4.2, you shouldn't use the return key as an explicit
> ...
>
> Joerg Kollmann NeXTMail welcome