If there's no mechanism to persist the app undo states and undo manager
messages, how should apps that support undo work with the automatic termination
behaviour ?
Should automatic termination be set dynamically and disabled when undo history
is present ?
A user might be annoyed if the undo hist
I don't think it's likely to be true in practice on 64-bit systems either. In
theory, yes, the old data could get paged out, and will not be paged back in
until the user uses it. In practice though, unless these pieces of old data are
big, contiguous buffers taking up pages by themselves, the o
On 25/03/2012, at 5:34 AM, Doug Clinton wrote:
> I don't know if this was the issue that Steven was asking about, but I've
> been wondering if there is a recommended way to persist the undo stack so
> that it's still available if you restart the app, or close and re-open the
> document. It's a
I think it's fair to say this is only true for a 64 bit app. In a 32 bit app,
it's fairly easy to exhaust your address space if all deleted files are kept
in-memory.
On 26 Mar 2012, at 00:57, Steven wrote:
> Thanks for the info Graham.
> I'm using NSUndoManager. I thought that many large objec
I don't know if this was the issue that Steven was asking about, but I've been
wondering if there is a recommended way to persist the undo stack so that it's
still available if you restart the app, or close and re-open the document. It's
always bothered me that there is this great mechanism for
Thanks for the info Graham.
I'm using NSUndoManager. I thought that many large objects in the stack would
cause memory pressure and would be better occupying disc space as they are only
needed at undo/redo time. Good to know that the VM system will take care of it.
Steven.
On 24 Mar 2012, at
You can read and write to the Application Support folder.
But FILES in an Undo stack? That makes little sense to me.
If you want to undo changes to a file, store the changes or the command that
will cause the changes in the undo stack. If you are changing the organisation
of files on disc then
Hello,
Where is the correct place to store an on-disc undo stack associated with a
NSDocument instance ?
The stack may contain several potentially large files so we don't want them to
occupy memory.
For a compound document the stack could reside in a directory NSFileWrapper.
For a single file do
