Bug 279774 - [Preferences] IpreferenceStore does not have a remove key option
Summary: [Preferences] IpreferenceStore does not have a remove key option
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3.2   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-10 06:13 EDT by Sujeet Mishra CLA
Modified: 2019-09-06 16:08 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sujeet Mishra CLA 2009-06-10 06:13:13 EDT
Our eclipse application is designed to dynamically add key/values to the preference store. We need a mechanism to remove a key from the preference store.
Comment 1 Paul Webster CLA 2009-06-10 08:50:51 EDT
The mechanism is definitely there in org.eclipse.core.runtime.preferences.IEclipsePreferences.  

Did you get them from org.eclipse.ui.plugin.AbstractUIPlugin.getPreferenceStore()?Are these for preferences that would have a default?  If not, org.eclipse.jface.preference.IPreferenceStore.setToDefault(String) might work for you since it removes the name (although it will set a default of "" if none specified).

PW
Comment 2 Sujeet Mishra CLA 2009-06-24 07:29:28 EDT
Hi Paul,
        Thanks for the information. It works fine , 

Yes we do use the org.eclipse.ui.plugin.AbstractUIPlugin.getPreferenceStore()
which gives us a ScopedPreferenceStore instance

If i can request a few methods on the IPreferenceStore implementation they would be 

1.a clear() method similar to java.util.prefs.Preferences
2.a removekey() method


Warm Regards
Sujeet


Comment 3 Eclipse Webmaster CLA 2019-09-06 16:08:57 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.