I just found a bug in XCode and Interface builder. (It was the reason for my problem in the thread I posted yesterday) It goes as follows: if you have an IBOutlet object of some name, and a set method using the same name, the IBOutlet object will become nil. I created a test project which you can download here. In it, I have an NSTextField test object (which I connect to testString), and I also have a setTestString method. I test to see if testString is nil, and output (in another NSTextField) whether it's nil or not. If you run it as-is, with the set method in, it's nil. If you comment out the set method, it's no longer nil. It's a good idea to keep this in mind if this happens to you, since I spent basically an entire day before I figured out something with the name was wrong. (I also experienced it a few times today, which then led me to the exact cause)

And yes, I already sent a bug report to Apple.

Are you sure that that's a bug? Official Apple documentation states that they will try to set the value for an outlet first with a set method, then directly. So if the outlet is called testString and you have a method called setTestString, IB will try to connect that outlet not by setting testString directly, but by calling setTestString.

I was wondering if that was the case, but I personally think that it should always directly set it. I don't know if other people rely on the set methods for connections, but I personally don't see any need for it. It's merely caused me trouble so far.

Some ideas as to why it may be useful:
http://www.cocoadev.com/index.pl?KeyValueCoding

Official Apple docs:
http://developer.apple.com/documentation...index.html

I use key codes. But not for IBOutlets that are connected through Interface Builder.

Edit: and IBOutlet connections were around long before key-codes were introduced in Panther, so it's not like they must rely on the key codes.