🚀 go-pugleaf

In article <1992Jul23.054852.11368@csus.edu>
	eps@futon.SFSU.EDU (Eric P. Scott) writes:
>In article <1992Jul22.212148.26961@aio.jsc.nasa.gov>
>	bill@epnxt.jsc.nasa.gov writes:
>>According to my docs, there is a SoundView class located at
>>View:Responder:Object.  I have ver 2.1 of the operating system
>>and do not find that class in IB.  Was it taken out?
<...>
>Note that IB won't have parsed the interface definition, so you
>won't be able to connect directly to the "reduction" or "sound"
>ids.
>
>If this disturbs you, there are two workarounds:
>
>	(1) Attempt Save As... to /usr/include/soundkit/UNTITLED
>	    [This SHOULD fail for lack of permissions!]
>	  -or-
>	(2) Create a symlink from /usr/include/soundkit/SoundView.h
>	    into your project directory (or home directory if you
>	    haven't created a project directory yet).
>
>	THEN Parse will work.  (If you used (2), you can remove the
>	symlink now.)

Or, drag the file from /usr/include/soundkit/SoundView.h and drop it
in the Classes suitcase or window (whichever is easiest).  Or, just
add the outlets manually in IB (just make certain the spelling is
correct).  Parsing and Unparsing in IB is simply a convenience
function that allows the user to easily update either IB or the .[hm]
file so that both have the same ideas about what exactly the class
looks like.  If you don't want to use that convenience - don't!  There
are many cases where IB doesn't do so well (Unparsing over top of
existant sources, or Parsing when you have instance variables like
Button *, or Parsing when you have Categories in the .h file), and
manually is the way to go ...

Later,
--
scott hess <shess@ssesco.com>  <Who's now in a programming Berserker-frenzy>
12901 Upton Avenue South, #326  Burnsville, MN 55337 (612) 895-1208 Anytime!
<I want to become so famous that people buy tapes of me reading source code>