fredd:

Adam,

 

Our users are very frustrated with this problem and our tech support people are inundated with complaints. Please don't suggest we use another editor or go back to a buggy previous version. We have paid you for this one and have invested a lot of time building a user framework around it. So we need to work with what we have.

 

What we want is simply to have an editor that our users can work with and that acts like any other text editor. From a user's viewpoint, they don't care about underlying technical issues -- they just want the product to work.

 

BTW, this Cutesoft ID (fredd) is used by all 3 of our support personnel. Some are more annoyed than others because they are frustrated with user complaints so sometimes their comments are a bit abrupt...

 

Doesn't make sense:

 

One of the biggest issues we have is that it makes no sense that we can type without any delays when there are only a few words in the content, but when there are thousands of words, each keystroke doesn't display at the same rate. Something is very out of whack here. It doesn't matter if we are typing at the beginning or end of a long document, the delay is the same. Is your code checking through the entire document on every keystroke? Why would this delay occur?

 

Identifying the delay:

 

When I load up the editor with 1000 lines of typing and type in normal view, the delay is very significant.

 

If I then switch to HTML view and type something, the editor still exhibits delays but the delay is quite a bit less than in the Normal view. There is still an annoying delay but because the HTML view is active I would think there should be no delay at all, assuming you are not monitoring key events in that mode...

 

Are you monitoring the key events even when CE is in the HTML view? If not, then why would there still be a delay in that mode?

 

I think if you can identify the reason for the delay when in the HTML view and eliminate it, it will help significantly to reduce the typing display delay in Normal view.

 

Another possibility: you have multi-undo levels built in so that must be taking some time each time a key is pressed. Could this be contributing to the delay?

 

And by the way, when I set EnableClientScript to false, there is no delay even when there is ten times as much content, so the problem definitely is in the interaction with script somewhere.

 

Thanks, Adam

FredD