Community
Participate
Working Groups
Steps: 1. Enable Window Working Set action group 2. Window > Working Sets > Edit > New 3. Select Plug-ins and Fragments 4. Make a selection 5. Type filter text 6. Clear filter text The result is that the previous selection is lost. The code is similar to Mylyn's multi-select combo box implementation that is used in the task editor (bug 292433): private class CheckboxFilteredTree extends FilteredTree { public CheckboxFilteredTree(Composite parent, int treeStyle, PatternFilter filter) { super(parent, treeStyle, filter); } @Override protected TreeViewer doCreateTreeViewer(Composite parent, int style) { return new CheckboxTreeViewer(parent, style); } @Override public CheckboxTreeViewer getViewer() { return (CheckboxTreeViewer) super.getViewer(); } } To fix it Mylyn manually tracks the selected items and has the following work around: @Override protected WorkbenchJob doCreateRefreshJob() { WorkbenchJob job = super.doCreateRefreshJob(); job.addJobChangeListener(new JobChangeAdapter() { @Override public void done(IJobChangeEvent event) { if (event.getResult() != null && event.getResult().isOK() && !getViewer().getTree().isDisposed()) { getViewer().setCheckedElements(selectedValues.toArray()); } } }); return job; }
Hitesh is now responsible for watching bugs in the [Viewers] component area.
This code is custom to PDE (there's no public FilteredCheckboxTree, see bug 220668).
True, but I believe the cause of the problem is still in CheckboxTreeViewer or FilteredTree.
>True, but I believe the cause of the problem is still in CheckboxTreeViewer or >FilteredTree. Well, they don't know of each other and it's currently created locally by PDE. The best path is to fix bug 220668 but even then PDE needs to adjust its code.
I've been working with an alternative FilteredCheckboxTree for PDE that might be able to be applied to this case. I'll assign it to myself, but I don't know if it will be worked on for 3.6.
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. -- The automated Eclipse Genie.