Bug 302809 - [Preferences] Add filter & lock parameter to show preferences command
Summary: [Preferences] Add filter & lock parameter to show preferences command
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   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: 2010-02-13 11:58 EST by Philipp Kursawe CLA
Modified: 2019-09-06 15:36 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipp Kursawe CLA 2010-02-13 11:58:32 EST
Currently the ShowPreferencePageHandler only accepts the propertyPageId. It would be a nice feature if it would also take a comma separated list of "displayedIds".
Also it would be nice of one could specify that the preference page filtering is locked (OPTION_FILTER_LOCKED).
I could provide a patch.
Comment 1 Boris Bokowski CLA 2010-02-22 22:30:46 EST
(In reply to comment #0)
> Currently the ShowPreferencePageHandler only accepts the propertyPageId. It
> would be a nice feature if it would also take a comma separated list of
> "displayedIds".
> Also it would be nice of one could specify that the preference page filtering
> is locked (OPTION_FILTER_LOCKED).
> I could provide a patch.

What would be the use case for this enhancement?
Comment 2 Philipp Kursawe CLA 2010-02-23 01:15:04 EST
Use case:
prevent the user from changing the filter, so only my preference page is shown. If there is such functionality exposed by the PreferencesUtil class, why not expose it to the accompanied command? 
Take the "Problems View" preference command handler. It overrides the preferences command instead of just displaying its preference page in the preference dialog. Currently it implements its own preference dialog. I filed a separate bug for that.
Comment 3 Eclipse Webmaster CLA 2019-09-06 15:36:19 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.