Forum Discussion
- hlalumiereRegular ContributorYou must be kidding Tanya, there are at least 5 other threads on this forum regarding the god-awful slow autocomplete by memory.
I don't think anyone who actually uses the code editor doesn't have problems with it. - googleid_105613Occasional ContributorYes, it's been bad since it was introduced. If you've got a small code base, it's not so bad, but with the more USEUNITs you put into your scripts, the worse it gets. We've got a code base with about 400 scripts, mostly library code. Generally, after a fresh install, once I notice that code editing is going slowly I turn off auto-complete it makes editing code more bearable, but if I hit CTRL-Space to find the function signature for a function, it's slow finding the function.
- hlalumiereRegular ContributorI think the main problem the SmartBear programmers have is their test codebase. It needs to be bigger. MUCH bigger than the average customer will ever have. Nick and I both have projects about the same size (mine is about 300 test units with each about 10 tests on average) and we both have the issue you guys apparently cannot reproduce. Get into the real world, please.
Hi Nick,
I didn't hear complains from the TestComplete 9.30 users about the slow appearing of the Code Completion window. The issue you faced may be specific to your situation. I recommend that you contact our TestComplete Support team to investigate this behavior.
- madamakisOccasional Contributor
Hello,
I agree with Nick's comments when the code is small it was farly quick but as time went on it started to slow down. I thought that was normal response from TC. Would be awesome if it gets fixed for the next release.
Mike
Hi Team,
Thanks for your responses!
Hugo, can you provide the TestComplete Support Team with your project? In this case, our R&D team will investigate the problematic behavior.
- hlalumiereRegular ContributorUnfortunately my employer won't allow it. Besides, we pay you guys lots of money to do this work, I shouldn't have to do anything on my end, especially for a problem so simple to diagnose. Look at the autocomplete code, any half good programmer would spot the bottlenecks a mile away.