Jump to: navigation, search

Difference between revisions of "FAQ How do I load and save plug-in preferences?"

 
m
Line 6: Line 6:
 
also operate on these plug-in preference stores.  
 
also operate on these plug-in preference stores.  
  
 +
Retrieving values from plug-in preferences is fairly straightforward:
  
 
 
Retrieving values from plug-in preferences is fairly straightforward:
 
 
<pre>
 
<pre>
 
   Plugin plugin = ExamplesPlugin.getDefault();
 
   Plugin plugin = ExamplesPlugin.getDefault();
Line 15: Line 13:
 
   int value = prefs.getInt("some.key");
 
   int value = prefs.getInt("some.key");
 
</pre>
 
</pre>
 +
 
When preferences are changed, the preference store must be
 
When preferences are changed, the preference store must be
 
explicitly saved to disk:
 
explicitly saved to disk:
 +
 
<pre>
 
<pre>
 
   prefs.setValue("some.key", 5);
 
   prefs.setValue("some.key", 5);
 
   plugin.savePluginPreferences();
 
   plugin.savePluginPreferences();
 
</pre>
 
</pre>
 
 
 
  
 
The plug-in preference store can also store default values for any
 
The plug-in preference store can also store default values for any
Line 34: Line 31:
 
a default value for each key by overriding the <tt>initializeDefaultPluginPreferences</tt>
 
a default value for each key by overriding the <tt>initializeDefaultPluginPreferences</tt>
 
method in your <tt>Plugin</tt> subclass:
 
method in your <tt>Plugin</tt> subclass:
 +
 
<pre>
 
<pre>
 
   protected void initializeDefaultPluginPreferences() {
 
   protected void initializeDefaultPluginPreferences() {
Line 40: Line 38:
 
   }
 
   }
 
</pre>
 
</pre>
 +
 
Although you can change default values at any time, it is generally advised
 
Although you can change default values at any time, it is generally advised
 
to keep them consistent so that users know what to expect when they
 
to keep them consistent so that users know what to expect when they
Line 45: Line 44:
 
a preference to its default value is accomplished with the <tt>setToDefault</tt>
 
a preference to its default value is accomplished with the <tt>setToDefault</tt>
 
method.
 
method.
 
 
 
 
 
  
 
== See Also: ==
 
== See Also: ==
 
+
*[[FAQ_How_do_I_use_the_preference_service%3F]]
 
+
[[FAQ_How_do_I_use_the_preference_service%3F]]
+
  
 
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font>
 
<hr><font size=-2>This FAQ was originally published in [http://www.eclipsefaq.org Official Eclipse 3.0 FAQs]. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the [http://www.eclipse.org/legal/epl-v10.html Eclipse Public License v1.0].</font>

Revision as of 22:05, 29 May 2006

Each plug-in has a local workspace preference store for saving arbitrary primitive data types and strings. Preferences displayed in the Workbench Preferences dialog are typically stored in these local plug-in preference stores. The Import and Export buttons in the Workbench Preferences page also operate on these plug-in preference stores.

Retrieving values from plug-in preferences is fairly straightforward:

   Plugin plugin = ExamplesPlugin.getDefault();
   Preferences prefs = plugin.getPluginPreferences();
   int value = prefs.getInt("some.key");

When preferences are changed, the preference store must be explicitly saved to disk:

   prefs.setValue("some.key", 5);
   plugin.savePluginPreferences();

The plug-in preference store can also store default values for any preference in that plug-in. If a value has not been explicitly set for a given key, the default value is returned. If the key has no default value set, a default default value is used: zero for numeric preferences, false for Boolean preferences, and the empty string for string preferences. If the default default is not appropriate for your preference keys, you should establish a default value for each key by overriding the initializeDefaultPluginPreferences method in your Plugin subclass:

   protected void initializeDefaultPluginPreferences() {
      prefs = plugin.getPluginPreferences();
      prefs.setDefault("some,key", 1);
   }

Although you can change default values at any time, it is generally advised to keep them consistent so that users know what to expect when they revert preferences to their default values. Programmatically reverting a preference to its default value is accomplished with the setToDefault method.

See Also:


This FAQ was originally published in Official Eclipse 3.0 FAQs. Copyright 2004, Pearson Education, Inc. All rights reserved. This text is made available here under the terms of the Eclipse Public License v1.0.