[Ghoser777]

I have a massive, monolithic nib file that I've been using forever, and now all of a sudden it's been misbehaving. Here's what happens:

1) If I go into IB and try to test the interface, I get several things printed to the Console log about all my custom classes not being found, so it's defaulting it's nearest superclass (usually NSObject). If I try to make new instances of my custom classes, they don't have those warnings posted.

2) If I build my project, it fails to launch (actually, it hangs and never posts NSApplicationDidFinishLaunching). But if I logout and log back in, it launches fine!

3) Because I have a lot of connections in my monolithic nib file, it's not going to be the most efficient solution for me to simply recreate my instances and my connections.

So, has anyone seen this before, or no of a good way to fix it (without recreating the instances and connections). Yes, this is a lesson in not making one, monolithic nib file.

Thanks,
Matt Fahrenbacher

[Angus_D]

Send it off to the Apple IB engineers (Henry Lamiraux or similar).

[Ghoser777]

Originally posted by Angus_D:
Send it off to the Apple IB engineers (Henry Lamiraux or similar).

Actually, nevermind. I just didn't realize that those error messages I was seeing were normal. It kind of makes since too, as IB only knows about the class definitions, and nothing about my compiled custom code (which would be necesary in instantiation).

My real problem was some code that magically stopped working and was being called during one of my initialization methods. I was sending an apple event to another application, telling it to quit, and it was hanging. I'm not really sure why, but commenting out that code fixed everything up.

Thanks,
Matt Fahrenbacher