Am 27.03.2008 um 11:57 schrieb Gerriet M. Denkmann:
On 26 Mar 2008, at 22:56, Graham Cox wrote:
The undo manager will directly change the data in the text view
using an invocation or target/action - it doesn't go back through
changeFont: normally, which is really a high level method.
On 27 Mar 2008, at 14:46, Jens Miltner wrote:
Am 27.03.2008 um 11:57 schrieb Gerriet M. Denkmann:
On 26 Mar 2008, at 22:56, Graham Cox wrote:
The undo manager will directly change the data in the text view
using an invocation or target/action - it doesn't go back through
changeFont:
The undo manager will directly change the data in the text view using
an invocation or target/action - it doesn't go back through
changeFont: normally, which is really a high level method.
Maybe the solution to this is to subclass NSUndoManager so that you
can hook into the undo and redo
has been changed.
This would imply that we have two kinds of changes: real changes
(like typing, cut and paste of text, etc.) and ephemeral changes
(e.g. change of font).
Both are recorded by the NSUndoManager, but only real changes make
the document dirty.
How could this be done
gets
stored.
So I would like that the document does NOT get dirty
(isDocumentEdited) if only the font has been changed.
This would imply that we have two kinds of changes: real changes
(like typing, cut and paste of text, etc.) and ephemeral changes
(e.g. change of font).
Both are recorded
