Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!rochester!pt.cs.cmu.edu!o.gp.cs.cmu.edu!andrew.cmu.edu!wb1j+ From: wb1j+@andrew.cmu.edu (William M. Bumgarner) Newsgroups: comp.sys.next Subject: Re: float c=[sliderA floatValue] won't compile-why? Message-ID: Date: 23 Jun 91 22:03:25 GMT References: <1163.2862231f@amy.skidmore.edu> Organization: Carnegie Mellon, Pittsburgh, PA Lines: 42 In-Reply-To: <1163.2862231f@amy.skidmore.edu> More likely than not, you haven't #imported the appropriate stuff: At the top of your .h or .m file do: #import // this imports only the Slider class declration or #import // this imports the whole bloody appkit-- slower, //but more convenient. See the warning below. --- You can use the #import to make your life managing the .h files easier, BUT, by doing this, you lose some of cc's ability to figure things out. As an example, if you have a Slider connected to an outlet and send a message that Slider doesn't implement to that outlet (but that some other class in the appkit does implement), then CC won't find the problem but your App will crash. I have found that by only including the classes that are neccessary, you gain several advantages: - cc will bitch if you haven't done the Right Thing (usually... there are certain cases where it won't) - You will have a much better understanding of exactly what classes are used in your application - compile times will be faster because cc doesn't have to include everything. hope this helps, b.bum b.bumgarner | Disclaimer: All opinions expressed are my own. wb1j+@andrew.cmu.edu | I officially don't represent anyone unless I NeXT Campus Consultant | explicity say I am doing so. So there. "I ride tandem with the random/Things don't run the way I planned them.."