We would like to report two issues that we have encountered:
- While stress testing our editor we found that using the WordHighlightTagger slowed down the editor to a point which is impossible to work with (1-2 seconds delay between a keystroke and a letter appearing even when using the original example in the Sample Browser itself). We found that the GetCurrentWordText is the most expensive (using the VS profiling). The document which we tested on it was approximately 300,000 characters long.
- On that same document we also used the editor.ActiveView.GetReader() (in the editor’s DocumentTextChanged event if that’s important to specify) and found out that the ReadTokenReverse function took an extremely long time to complete.
In a few other places, reader.Token also took quite some time to execute.
Do you know why it might happen? What options do we have if we need to use the editor with such long documents?
Asaf & Tal