Rational Developer for Power Systems Software
V7.6

com.ibm.etools.systems.application.visual.editor.ui.preferences
Class SystemGraphicalEditorPreferencePage

java.lang.Object
  extended by FieldEditorPreferencePage
      extended by com.ibm.etools.systems.application.visual.editor.ui.preferences.SystemGraphicalEditorPreferencePage

public class SystemGraphicalEditorPreferencePage
extends FieldEditorPreferencePage

Preference page specifies diagram layout settings.


Field Summary
static String copyright
           
protected  Label imageLabel
           
 
Constructor Summary
SystemGraphicalEditorPreferencePage()
          Constructor.
 
Method Summary
protected  void createFieldEditors()
           
protected  void createPreferenceEntries(Composite main)
          Create preference field entries.
 void init(IWorkbench workbench)
           
static void initDefaults(IPreferenceStore store)
          Initialize from preference store.
 void modifyText(ModifyEvent e)
           
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Field Detail

copyright

public static final String copyright
See Also:
Constant Field Values

imageLabel

protected Label imageLabel
Constructor Detail

SystemGraphicalEditorPreferencePage

public SystemGraphicalEditorPreferencePage()
Constructor.

Method Detail

initDefaults

public static void initDefaults(IPreferenceStore store)
Initialize from preference store.

Parameters:
store -

createPreferenceEntries

protected void createPreferenceEntries(Composite main)
Create preference field entries.

Parameters:
main -

createFieldEditors

protected void createFieldEditors()

init

public void init(IWorkbench workbench)

modifyText

public void modifyText(ModifyEvent e)

Rational Developer for Power Systems Software
V7.6

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.