Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 345718

Summary: [Preferences] jface PreferenceDialog could use the methods currently only in workbench FilteredPreferenceDialog
Product: [Eclipse Project] Platform Reporter: Joonas Koivunen <joonas.koivunen>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: eclipse.felipe, prakash, remy.suen
Version: 4.1   
Target Milestone: ---   
Hardware: PC   
OS: Linux   
Whiteboard: stalebug

Description Joonas Koivunen CLA 2011-05-13 07:23:00 EDT 
Build Identifier: 20110301-1815

org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog has the public methods to control what page is currently shown, yet this kind of functionality should be considered something that "PreferenceDialog" has, it's not tied to "FilteredPreferenceDialog" in any way.

In addition, plain PreferenceDialog has a curiously named "setSelectedNode" method which does nothing what the name implies; it'd expect it to select the given node and reveal this selection (just what FilteredPreferenceDialog#setCurrentPageId() does).

I stumbled upon all this while searching how links are implemented in the current eclipse preference dialog, hoping to use the same functionality in my standalone swt/jface application.

So what I suggest:

Move FilteredPreferenceDialog#setCurrentPageId(String) to jface Preference dialog. There might be more of these and I'll add them as comments later on, should I find such.

Build-ID is most likely incorrect against the versions I use in my standalone, but this can be found from the eclipse CVS head of this date.

Reproducible: Always
Comment 1 Lars Vogel CLA 2019-11-14 02:14:33 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.