Some anoying bugs in Carbide.c++

[daleng]

Hi and thanks for the new Carbide.c++ Eclipse based IDE

Having been a beta tester it is now good to see that Carbide c++ express has reached 1.0. There are however still some annoying hickups. I don't know if this is the right forum for this, but here some of them:

• There are absolute paths to the workspace in the .settings/org.eclipse.cdt.managedbuilder.core.prefs file which makes sharing the project via version-control systems difficult. We are using Subversion with the Subclipse eclipse plugin, and has experienced a host of problems due to this.
• The settings files are not checked for changes prior to writing to them, which makes it challenging to manage a project using version-control systems since the in-memory settings will overwrite the incoming settings from version control. Since there is no mmp-file, this applies to all project the settings that previously were admittingly cumbersome to manage but more easily sharable than now.
• Automatic building does not work properly when working with header files.
• The debugger seems to not always able to show the value of local variables. They show up correctly when printed to the console, so this is most likely a debugger issue.

Carbide c++ has the potential to become a very good environment for developing Symbian applications, given that the initial bugs are resolved. Keep up the good work.

[msalmo]

Thanks for posting these issues, I will look into them for you and get back to you on this.