Nswindowcontroller failed to load window nib file

The raw data for the entire nib object graph is loaded into memory but is not unarchived. Any custom image resources associated with the nib file are loaded and added to the Cocoa image cache; see About Image and Sound Resources. Any custom sound resources associated with the nib file are loaded and added to the Cocoa sound cache; see About Image and Sound Resources. It unarchives the nib object graph data and instantiates the objects.

How it initializes each new object depends on the type of the object and how it was encoded in the archive. The nib-loading code uses the following rules in order to determine which initialization method to use. In OS X, the list of standard objects includes the views, cells, menus, and view controllers that are provided by the system and available in the default Xcode library. It also includes any third-party objects that were added to the library using a custom plug-in. Even if you change the class of such an object, Xcode encodes the standard object into the nib file and then tells the archiver to swap in your custom class when the object is unarchived.

Custom views are subclasses of NSView for which Xcode does not have an available implementation. Typically, these are views that you define in your application and use to provide custom visual content. Custom views do not include standard system views like NSSlider that are part of the default library or part of an integrated third-party plug-in.

The custom view object includes the information it needs to build the real view subclass you specified. At load time, the NSCustomView object sends an alloc and initWithFrame: message to the real view class and then swaps the resulting view object in for itself. The net effect is that the real view object handles subsequent interactions during the nib-loading process.

Custom objects other than those described in the preceding steps receive an init message. It reestablishes all connections actions, outlets, and bindings between objects in the nib file. The approach for establishing connections differs depending on the platform:. For each outlet, Cocoa looks for a method of the form set OutletName : and calls it if such a method is present. If it cannot find such a method, Cocoa searches the object for an instance variable with the corresponding outlet name and tries to set the value directly.

If the instance variable cannot be found, no connection is created. Setting an outlet also generates a key-value observing KVO notification for any registered observers.

These notifications may occur before all inter-object connections are reestablished and definitely occur before any awakeFromNib methods of the objects have been called.

In iOS, the nib-loading code uses the setValue:forKey: method to reconnect each outlet. That method similarly looks for an appropriate accessor method and falls back on other means when that fails. If the target object does not respond to the action method, no connection is created. If the target object is nil , the action is handled by the responder chain. If the target is nil , the action is handled by the responder chain.

In OS X, Cocoa uses the bind:toObject:withKeyPath:options: method of the source object to create the connection between it and its target object. It sends an awakeFromNib message to the appropriate objects in the nib file that define the matching selector :. In OS X, this message is sent to any interface objects that define the method.

In iOS, this message is sent only to the interface objects that were instantiated by the nib-loading code. The order in which the nib-loading code calls the awakeFromNib methods of objects is not guaranteed. If you need to configure the objects in your nib file further at load time, the most appropriate time to do so is after your nib-loading call returns. At that point, all of the objects are created, initialized, and ready for use.

Each time you ask the NSBundle or NSNib class to load a nib file, the underlying code creates a new copy of the objects in that file and returns them to you. The nib-loading code does not recycle nib file objects from a previous load attempt. You need to ensure that you maintain the new object graph as long as necessary, and disown it when you are finished with it.

Outlets that you create should therefore typically be weak , because:. Outlets are generally considered private to the defining class; unless there is a reason to expose the property publicly, hide the property declarations a class extension.

For example:. These patterns extend to references from a container view to its subviews where you have to consider the internal consistency of your object graph. For example, in the case of a table view cell, outlets to specific subviews should again typically be weak. If a table view contains an image view and a text view, then these remain valid so long as they are subviews of the table view cell itself.

Outlets should be changed to strong when the outlet should be considered to own the referenced object:. You may in some situations need an object from a nib file to exist outside of its original container. For example, you might have an outlet for a view that can be temporarily removed from its initial view hierarchy and must therefore be maintained independently. Classes that you expect to be subclassed in particular abstract classes expose outlets publicly so that they can be used appropriately by subclasses e.

Outlets might also be exposed where there is an expectation that consumers of the class will need to interact with the property; for example a table view cell might expose subviews.

In this latter case, it may be appropriate to expose a read-only public outlet that is redefined privately as read-write, for example:. For historical reasons, in OS X the top-level objects in a nib file are created with an additional reference count.

The Application Kit offers a couple of features that help to ensure that nib objects are properly released:. NSWindow objects including panels have an isReleasedWhenClosed attribute, which if set to YES instructs the window to release itself and consequently all dependent objects in its view hierarchy when it is closed. Action methods use type qualifier IBAction , which is used in place of the void return type, to flag the declared method as an action so that Xcode is aware of it.

You may choose to regard action methods as being private to your class and thus not declare them in the public interface. Because Xcode parses implementation files, there is no need to declare them in the header. You should typically not invoke an action method programmatically.

If your class needs to perform the work associated with the action method, then you should factor the implementation into a different method that is then invoked by the action method. The AppKit and UIKit frameworks both provide a certain amount of automated behavior for loading and managing nib files in an application. The following sections describe the built-in support for nib files, how you can take advantage of it, and ways to modify that support in your own applications.

Most of the Xcode project templates for applications come preconfigured with a main nib file already in place. All you have to do is modify this default nib file in the nib file and build your application. When an application is first loaded, the default application startup code looks in the Info.

If it finds it, it looks in the application bundle for a nib file whose name with or without the filename extension matches the value of that key and loads it. Any connections between the view controller and the nib file objects are created automatically, and in iOS, the UIViewController object also receives additional notifications when the views are finally loaded and displayed on screen. To help manage memory better, the UIViewController class also handles the unloading of its nib file as appropriate during low-memory conditions.

In the AppKit framework, the NSDocument class works with the default window controller to load the nib file containing your document window. The windowNibName method of NSDocument is a convenience method that you can use to specify the nib file containing the corresponding document window. When a new document is created, the document object passes the nib file name you specify to the default window controller object, which loads and manages the contents of the nib file.

If you use the standard templates provided by Xcode, the only thing you have to do is add the contents of your document window to the nib file. The NSWindowController class also provides automatic support for loading nib files. Connect and share knowledge within a single location that is structured and easy to search. The error you have described ultimately occurs because a call to load the nib file is failing. Make sure you've supplied the correct name for your Interface Builder file.

You can supply the correct value in a number of ways depending on your use of AppKit , so I'll lay out the two most common possibilities and you can track down which one applies to you. Given what you've said in your question, I suspect you'll be dealing with the first scenario. If you are relying on the document architecture's defaults, you are probably not making the call in question directly. Instead, the framework makes the call on your behalf, using whatever nib name you specify on the given document class.

The XYZDocument implementation file would have the following in it:. If you are making this call yourself perhaps on your own subclass of NSWindowController , then you will have written a line like the following. If the string argument you've supplied does not match the name of the nib file, the same error will occur. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more.

Ask Question. Asked 9 years, 3 months ago. Active 6 years, 3 months ago. Do a backup. Boot to the Recovery Volume command - R on a restart or hold down the option key during a restart and select Recovery Volume. Then reinstall the OS. Nov 30, PM. Question: Q: System wide failure to load. Communities Get Support. Sign in Sign in Sign in corporate. Browse Search. Ask a question. User profile for user: valisj valisj. Question: Q: Question: Q: System wide failure to load. But the application is not getting terminated.