Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 344843 - [Viewers] TreeViewer updatePlus() doesn't consider the ViewerFilters
Summary: [Viewers] TreeViewer updatePlus() doesn't consider the ViewerFilters
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-05 10:10 EDT by Danail Nachev CLA
Modified: 2019-11-27 07:32 EST (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 Danail Nachev CLA 2011-05-05 10:10:53 EDT
I have a TreeViewer with a content provider and viewer filter. After remove() is called to remove all visible children (there are still children, but they are filtered out), the tree shows a plus sign and because the node was initially expanded, the dummy item added to the tree is shown as well.

After some debugging the problem appears to lie in updatePlus() which is called from internalRemove() to remove the plus sign if there are no more children (fix for bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=210747). updatePlus() consider only the information retrieved from the ContentProvider, but ignore the fact that the children might be filtered out later.

I've tried to work around the problem by using refresh() instead of remove(), but the problem is still there.
Comment 1 Lars Vogel CLA 2019-11-27 07:32:04 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.