Bug 62095 Compiler pref page should be more resilient
Build 20040513 When patching with latest JDTCore, with adjusted constant value for EmptyStatement optional warning, I saw the following entry in console. 1. it shouldn't be shown by default I suspect, only when in trace mode. 2. when option isn't readable it shouldn't be promoted to ERROR as observed when then looking at pref page. It should rather be turned back to IGNORE. !ENTRY org.eclipse.jdt.ui 4 10001 May 13, 2004 15:37:08.30 !MESSAGE preference option missing: org.eclipse.jdt.core.compiler.problem.superfluousSemicolon (org.eclipse.jdt.internal.ui.preferences.CompilerConfigurationBlo ck) !ENTRY org.eclipse.jdt.ui 4 10001 May 13, 2004 15:37:15.721 !MESSAGE preference option missing: org.eclipse.jdt.core.compiler.problem.superfluousSemicolon (org.eclipse.jdt.internal.ui.preferences.CompilerConfigurationBlo ck)
org.eclipse.jdt.ui/ui/org/eclipse/jdt/internal/ui/preferences/OptionsConfigurationBlock.java
updateText((Text) fTextBoxes.get(i));
		}
	}
	
	protected void updateCombo(Combo curr) {
		ControlData data= (ControlData) curr.getData();
		
		String currValue= (String) fWorkingValues.get(data.getKey());	
		curr.select(data.getSelection(currValue));					
	}
	
	protected void updateCheckBox(Button curr) {
		ControlData data= (ControlData) curr.getData();
		
		String currValue= (String) fWorkingValues.get(data.getKey());	
		curr.setSelection(data.getSelection(currValue) == 0);						
	}
	
	protected void updateText(Text curr) {
		String key= (String) curr.getData();
		
		String currValue= (String) fWorkingValues.get(key);
		if (currValue != null) {
			curr.setText(currValue);
		}
	}
	
	protected Button getCheckBox(String key) {
		for (int i= fCheckBoxes.size() - 1; i >= 0; i--) {
			Button curr= (Button) fCheckBoxes.get(i);