Fix bug where launch configs created from Executables view need to be saved after editing
authorEd Swartz <ed.swartz@nokia.com>
Wed, 07 Jul 2010 14:03:56 -0500
changeset 1590 39ba239eeb5c
parent 1587 c7ab3cbf655a
child 1593 09779f4a10b3
Fix bug where launch configs created from Executables view need to be saved after editing
debuggercdi/com.nokia.cdt.debug.cw.symbian/src/com/nokia/cdt/debug/cw/symbian/SettingsData.java
--- a/debuggercdi/com.nokia.cdt.debug.cw.symbian/src/com/nokia/cdt/debug/cw/symbian/SettingsData.java	Wed Jul 07 11:40:40 2010 -0500
+++ b/debuggercdi/com.nokia.cdt.debug.cw.symbian/src/com/nokia/cdt/debug/cw/symbian/SettingsData.java	Wed Jul 07 14:03:56 2010 -0500
@@ -680,9 +680,8 @@
 		if (project != null) {
 			configuration.setMappedResources( new IResource[] { project });
 		    ICarbideProjectInfo cpi = CarbideBuilderPlugin.getBuildManager().getProjectInfo(project);
-			if (cpi != null) {
-				configuration.setAttribute(ICDTLaunchConfigurationConstants.ATTR_PROJECT_BUILD_CONFIG_ID, cpi.getDefaultBuildConfigName());
-			}
+		    configuration.setAttribute(ICDTLaunchConfigurationConstants.ATTR_PROJECT_BUILD_CONFIG_ID, 
+		    		cpi != null ? cpi.getDefaultBuildConfigName() : ""); //$NON-NLS-1$
 		}
 		
 		// set rom log file defaults.  do this for all launch types since it shouldn't hurt