Access to the Undo list

Hi Kasper,

Unfortunately since the undo/redo data is tracked internally, it is a read-only collection on the Document.

However, we made the Document object so that it can be used independently from SyntaxEditor. Along with that design, it is portable, meaning you can retain a reference to the Document and then reassign it to the SyntaxEditor later. While it is detached from the SyntaxEditor, it will retain the Undo/Redo information. Could you do that?

>Unfortunately since the undo/redo data is tracked internally, it is a read-only collection on the Document.

Okay, I'm not trying to be clever or anything, but if you allowed access to it, and I did not try to remove or add items directly to it, but simply assigned it to the SyntaxEditor - would this cause problems?

>However, we made the Document object so that it can be used independently from SyntaxEditor. Along with that design, it is portable, meaning you can retain a reference to the Document and then reassign it to the SyntaxEditor later. While it is detached from the SyntaxEditor, it will retain the Undo/Redo information. Could you do that?

Yeah, it seems to work, but won't this require a bunch of extra memory, for each open document I have? I'm using only one instance of SyntaxEditor because it seems to save some memory when multiple documents are open. However, the Document seems to be a big part of the memory usage, including the SyntaxLanguage - or am I wrong here? :)

[Modified at 05/31/2006 10:42 AM]

Since it is an internal class that stores the undo info, we can't allow it to be persisted externally. So our recommendation is to save the Document.

The Document stores data for text, document lines, undo/redo, indicators, and tokens. You want the undo/redo. If you aren't using indicators, that won't take up anything. So that leaves the memory taken up for text, document lines and tokens.

In the work we've done on v4.0, the document line memory usage has been reduced dramatically. It scales up though as needed if you start using extra features like background colors, etc. Also in v4.0 we allow you to turn off lexical parsing, meaning it clears the tokens. Therefore when you are storing a Document in memory, you could turn off the lexical parsing until you want to plug it back into a SyntaxEditor. Those things will really cut down the memory footprint.