Browse Source
GUI renderers/editors: Move from static allocation to allocation on first use
GUI renderers/editors: Move from static allocation to allocation on first use
Currently, most of the Setting classes construct a SettingRenderer and SettingEditor statically, for use in the GUI. When running PRISM from the command-line (PrismCL), we make sure to run Java in headless mode and generally those calls then don't matter. If there are problems with the AWT configuration, there can be exceptions even for PrismCL. So, here, we switch from static allocation on class loading to static allocation on first use of getSettingsEditor() and getSettingsRenderer().master
committed by
Dave Parker
9 changed files with 68 additions and 74 deletions
-
15prism/src/settings/BooleanSetting.java
-
24prism/src/settings/ChoiceSetting.java
-
14prism/src/settings/ColorSetting.java
-
15prism/src/settings/DoubleSetting.java
-
15prism/src/settings/FontColorSetting.java
-
15prism/src/settings/IntegerSetting.java
-
15prism/src/settings/LongSetting.java
-
15prism/src/settings/MultipleLineStringSetting.java
-
14prism/src/settings/SingleLineStringSetting.java
Write
Preview
Loading…
Cancel
Save
Reference in new issue