I'm working on a rather big project bld.inf with some 30 MMPs.
After changing some code and rebuilding my Symbian component using CTRL+ALT+B I click the Debug button expecting the emulator to start instantly. Instead Carbide systematically wants to rebuild the whole project which takes at least 5 minutes on a very fast dual core machine.
As a workaround I interrupt the build process kicked off after clicking the Debug button and then I click again the Debug button this time it launches the emulator without trying the rebuild the whole project.
Also sometimes after a debug session it just can't build my component any more saying that the EXE is used by another process. To fix it I have to exit and restart Carbide.
BTW, overall I'm very very happy with Carbide.C++ v1.2 so far. The code browsing notably is simply amazing it really makes a huge difference in productivity. I particularly appreciate things like Call Hierarchy and Type Hierarchy. Keep up the good work Carbide people! I'll be looking forward for a consolidated v1.3.