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

Bug 263035

Summary: [Dialogs] Filtered List: Provide access to fList field
Product: [Eclipse Project] Platform Reporter: Tatiana Fesenko <tatiana.fesenko>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: enhancement    
Priority: P3 CC: heiko.boettger, Mike_Wilson, pwebster
Version: 3.5Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Tatiana Fesenko CLA 2009-01-30 09:07:32 EST
FilteredList is commonly used. And it's natural for its clients to add DoubleClickListeners. It's possible using TableViewer for fList field. However, fList has private visibility. 
Please, provide access to fList field, or its TableViewer, in order to allow clients to add DoubleClickListener.
Comment 1 Mike Wilson CLA 2009-05-05 12:51:38 EDT
Changing Version tag to something more believable. Note that this is not a statement about when the enhancement request will be addressed (the Target Milestone field is used for that); the Version tag should be set to the version of Eclipse you were using when you saw the need for the enhancement.
Comment 2 Susan McCourt CLA 2009-07-09 18:20:26 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Heiko Böttger CLA 2012-08-31 08:53:12 EDT
Searching for the same possibility here, we currently use a hack, by searching through the widget hierarchy. Additionaly there should be the possibility to extend the post update code in the UpdateJob. In our case we specified a checkbox style table which requires to set the checked state.
Comment 4 Lars Vogel CLA 2019-11-27 07:26:46 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.