Question

In the Implementation Overview section of the NSPersistentDocument Core Data Tutorial it says:

1. …
2. One issue with creating the new top-level object in the nib file is that when you use bindings an object retains other objects to which it is bound. This means that bindings must be broken to ensure there are no retain cycles when a document is closed. Moreover, since the nib file the new controller owns contains top level objects and the controller’s class does not inherit from NSWindowController, you need to release the top level objects when the window is closed.

Why not just have the controller inherit from NSWindowController? Is there a reason this would not work? Or was this just a matter of style?

Answer 1

As commented below, I did get this to work with an NSWindowController subclass, and it does seem to save quite a bit of code.

Here is my subclass header:

#import <Cocoa/Cocoa.h>

@interface NewAccountSheetController : NSWindowController {
@private
    BOOL isValidForInsert;
    NSManagedObjectContext * managedObjectContext;
    NSObjectController * objectController;
    NSObjectController * targetController;
}

@property (setter=setValidForInsert:) BOOL isValidForInsert;
@property (nonatomic, retain) IBOutlet NSManagedObjectContext * managedObjectContext;
@property (nonatomic, retain) IBOutlet NSObjectController * objectController;
@property (nonatomic, retain) IBOutlet NSObjectController * targetController;

- (void)beginSheetForWindow:(NSWindow *)window;

- (IBAction)endSheet:(id)sender;

@end

And here is the implementation in a Pastebin.

I have no good idea how to describe the required bindings, etc. but if you’re familiar with the above tutorial they should be straightforward to extrapolate… I think. 🙂