Problem with GetSubstring

Hi Karl,

In v4.0 we changed things so that the Document.Text property returns the document text using CR/LF line ends since that is more naturally used. The reason we did this is that a lot of people would just save off the Document.Text to a file and then find that they saved LF-only terminated lines and not CR/LF like they thought.

Internally SyntaxEditor stores line ends as LF only while editing a document. This is to make it easy for parsing since you know exactly what character is there and that there is only one character flagging a line end. The Document.Length will return the number of characters in the document counting only one LF character for each line.

So to sum up, Document.Text.Length will NOT equal Document.Length if you have more than one line. In fact, for performance reasons and because of the problem you are experiencing, you should ALWAYS use Document.Length instead of Document.Text.Length since the latter constructs an entire string of the document and will be much slower than calling Document.Length.

Back to your case, you can do this: Please note that the smaller overload of GetSubstring will also perform like the Document.Text property and will return CR/LF. There is an overload of it that lets you indicate if you want a different LineTerminator though such as LF-only. There also is a Document.GetText which takes a LineTerminator and returns the same as the Document.Text property but lets you indicate which type of LineTerminator to use for the text.

Hope that helps explain it.

Thanks a lot for the reply.

I noticed that SyntaxEditor now used CR/LF in the text and I'd just assumed that internally you were doing the same.

Regards,

Karl

We stuck with LF for internals because it's easier to always know that there is one character that marks a line terminator instead of two.