"Thanks for the lack of help guys....."

 

Nice post. I'm sure that really encourages us to help you out.

 

 

I was aiming it more at the cutesoft support crew. They seem to have a lack of customer care going on. Anything slightly difficult they ignore. Seems to be a stick a head in the sand scenario and hope it goes away.

 

Fredd its great that you are answering so many threads, but surely thats cutesoft job, and sorry for the comment, it wasnt aimed at you.

 

As you have rightly said before a simple acknowledgement of the post and further replies to questions asked would not go amiss. Even if it is to say sorry they cannot do anything for a week, or it will be in next release dated xxx.

 

I have tried to be positive throughout, but there is only so many times you can listen to the "it works fine here" statement. My theory is if it breaks on one network, then its bound to have a similar problem elsewhere and as it turns out, its a very simple 3 char fix.

 

So Adam just to prove you do read all the threads etc. and in order to close this thread can you answer the following couple of questions as asked previously....

 

thanks

 

PS. in spite of all this, I do think the editor is still one of the best on the market and hope it still improves. If it wasnt I would have been long gone by now.

I've run into similar problems in a site where I'm using the editor as well.  However, I've got users with all kinds of browsers using the site.  They load a page with the editor and many times it is snappy.  Other times the same page will load, but they will wait for a while in order to be able to actually edit content in the site. 

 

I'm going to give the image editing a shot and see what happens.  I started to apply the same switch from .png to .gif across all of the various loaders and discovered that blank2020.png is only in the IE loader.  The other loaders all use the blank2020.gif file already.  So, that makes me think it may do something for IE, but I'm not sure what to do with the others.

 

Interestingly enough, I can manifest a problem in my development environment pretty quickly.  I load a page up a couple of times through Visual Studio.  By the 3rd or 4th trip I'll get my development environment to basically hang waiting on these files to download for the editor to activate.  I end up having to kill the debugger instance and relaunch the site, on which everything works ok for a bit, then will eventually come to a screeching halt in Visual Studio again.

We've updated the control and replace blank2020.png with blank2020.gif.

 

Please try again and keep me posted.

 

Download:

 

 

Demo:

 

 

 

Hi mstrawmyer

 

We only had this issue on IE6, and as you rightly say its only in the IE loader that this file exists. In tests Firefox for us has always been ultra fast, but most of our users use IE6, or IE5.5. Interesting how your experience seems to be similar as ours, I thought I was going doo laaly tat being the only one with this problem.

 

My gut feeling is that load.ashx is a bottle neck as its being called loads of times to load scripts, images etc. If for some reason .NET slows down this is used so much its a possible crunch point. I can see why they are using it as it makes coding a lot easier just changing some params, but it is an overhead as far as downloading files is concerned, IIS could download them much more efficiently without getting .NET involved.

 

When you make it hang in Visual studio whats the memory and CPU usage like?

Is anything on the machine busy?

Can you press the pause button in VS? Where does it take you too?

 

Anyway thanks Adam for the latest update, dont forget to update your change log, looks like some other files were changed as well as IE loader.

 

cheers