So what's the actual error (the title of the email seems incomplete)? If NSProxy is the receiver, that's most likely the NSProxy that NSUndoManager returns from -prepareWithInvocationTarget: The proxy should forward absolutely everything to the NSUndoManager, except possibly certain messages that for some reason it is excluding for reasons of its own. If you can determine exactly what the message is, look for the same one following a -prepareWithInvocationTarget: and you should have your culprit.
Debugging Undo issues can be a real PITA, which is one reason I wrote a drop-in replacement, GCUndoManager (http://apptree.net/gcundomanager.htm). It gives you the chance to at least see what's going on even though its implementation is very different from NSUndoManager's. --Graham On 21/08/2013, at 2:58 PM, Shane Stanley <sstan...@myriad-com.com.au> wrote: > On 21/08/2013, at 10:03 PM, Graham Cox <graham....@bigpond.com> wrote: > >> The arguments are retained, but the target is not. Does knowing that make >> any difference to your memory managment analysis? > > I don't think so. The target is the window controller in a document-based > app, created with -initWithWindowNibName: and added to the document with > -addWindowController: in its -makeWindowControllers method. Pretty basic. I > would have thought it wouldn't go away as long as its window is open. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
