On Aug 29, 2009, at 13:01, Jerry Krinock wrote:
Apparently when -[NSDocument undoManager] sees that its undo manager
is nil (because I set it to nil), it says to itself, Golly, we need
an undo manager here. So it creates one, sets it in the subclass -
[NSPersistentDocument
Well, I've got a background worker process which opens an
NSPersistenDocument. Since it has no undo capability, I want to set
it to nil as recommended. (I have other reasons for not wanting an
undo manager scurrying around.) But the document doesn't like having
nil undo manager. When I ask
On 2009 Aug 29, at 13:41, Quincey Morris wrote:
AFAIK, the problem is that NSPersistentDocument overrides *some* of
NSDocument's undo-related methods, but not all, and calling the un-
overridden ones really messes things up -- you can end up with 2
undo managers, one in a NSDocument private
