S60 Open to new features

We used to get a lot of complaints about Carbide performance with the first releases. Slow to launch, slow to import a project, slow to launch a debug session, slow to launch the emulator, slow to build, to step, etc. We always try to improve the performance of the toolset. Here are some areas that were addressed in releases 1.3 and 1.3.1

When importing the project into the workspace, the indexer was taking a lot of time running, making the impression that importing of a project takes forever. Carbide C++ v1.3 reduces time that indexer takes doing its work dramatically, so project importing is much faster now.

Substantially improved build time when only minor changes were done to the sources and consequent rebuild. This is the scenario that the developers experience most often. Here is some benchmarking data:

For on-device debugging we discovered that loading of symbolics file of 520 MB was taking more then 2 minutes and reduced that time to 30 seconds. So launching of the debug session is improved by the same delta.
Faster breakpoints resolution is another performance area worth mentioning.

What is your biggest concern with Carbide performance?
We will not be able to fix it unless you let us know!