Bug 76122 - [Viewers] JFace filters need to have dispose() method
Summary: [Viewers] JFace filters need to have dispose() method
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-10-12 16:08 EDT by Randy Hudson CLA
Modified: 2019-09-06 16:10 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 Randy Hudson CLA 2004-10-12 16:08:50 EDT 
A filter can be as dynamic as a content provider.  Currently, ContentProvider 
has a dispose method, but filters do not.  The workaround is to hook the 
Control's dispose method, AND to check to see if the filter is active before 
telling the viewer to refresh.

It would be easier if the viewer disposed the filter when:
1) The filter was no longer active
2) The viewer is disposed
Comment 1 Thomas Schindl CLA 2007-02-01 12:18:00 EST 
well I think this not possible because a Filter can be used in more than one viewer so we would have the strange situation that the first viewer is getting disposed => disposing its filters but another filter also uses one of the filter and suddenly it holds a disposed filter.
Comment 2 Randy Hudson CLA 2007-02-01 13:33:24 EST 
(In reply to comment #1)
> well I think this not possible because a Filter can be used in more than one
> viewer so we would have the strange situation that the first viewer is getting
> disposed => disposing its filters but another filter also uses one of the
> filter and suddenly it holds a disposed filter.

Wouldn't the same solution that is used for content providers apply? Couldn't each viewer have its own instance of the filter?
Comment 3 Boris Bokowski CLA 2009-11-26 09:49:49 EST 
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:10:55 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.