Bug 298917 - [Dialogs] ContainerSelectionDialog is not extensible enough due to a hardcode behavior in ContainerSelectionGroup
Summary: [Dialogs] ContainerSelectionDialog is not extensible enough due to a hardcode...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-05 22:36 EST by Khoa Nguyen CLA
Modified: 2019-09-06 16:04 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Khoa Nguyen CLA 2010-01-05 22:36:34 EST 
Build Identifier: All

I intend to use ContainerSelectionDialog to show up a folder chooser which is restricted to one and only one project. However, it always shows a whole workspace instead and I can't do anything to change this behavior. This is because in ContainerSelectionGroup, developers put the following code in createTreeViewer(int heightHint):

// This has to be done after the viewer has been laid out
treeViewer.setInput(ResourcesPlugin.getWorkspace());

I know ContainerSelectionDialog serves the purpose of workspace-wide folder choosing very well but if you could make it more flexible than a lot of people are very appreciated it.

Reproducible: Always

Steps to Reproduce:

Please allow to customize the input of treeViewer in ContainerSelectionGroup from ContainerSelectionDialog.
Comment 1 Remy Suen CLA 2010-01-06 07:50:05 EST 
I heartily support this enhancement request. I could've used the same thing back in 2007.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:04:42 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.