Bug 151819 - [Viewers] ContentProvider's getElements is not called (on specific Inputs)
Summary: [Viewers] ContentProvider's getElements is not called (on specific Inputs)
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL: http://www.privatepanic.de/tableviewe...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-07-26 07:28 EDT by Tim München CLA
Modified: 2019-09-06 15:31 EDT (History)
1 user (show)

See Also:


Attachments
example code (1.34 KB, text/plain)
2006-07-26 07:29 EDT, Tim München CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tim München CLA 2006-07-26 07:28:53 EDT
I have a TableViewer, and a ContentProvider that implements IStructuredContentprovider.

When setting the input of the tableviewer to a concrete Object (that is not null), inputChanged() is called at the content provider, but getElements() is not. If, however, I create an ArrayList with only the mentioned Object in it, and pass that to setInput(), getElements() fires.
Comment 1 Tim München CLA 2006-07-26 07:29:55 EDT
Created attachment 46809 [details]
example code
Comment 2 Thomas Schindl CLA 2006-07-26 07:33:12 EDT
Please provide a stand-alone example runnable by anybody without needing to code anything.
Comment 3 Thomas Schindl CLA 2006-07-26 08:08:22 EDT
Moreover if you are already using a viewer you should not grab all those informations from the tableItem.

-------------8<-------------
TableItem [] ti = table_Bestellpositionen.getSelection();
...
-------------8<-------------

Why not wrap your table_Bestellpositionen into a TableViewer and call viewer.getSelection().
Comment 4 Boris Bokowski CLA 2006-07-28 11:40:06 EDT
Is anything in your .log?  Do you use a virtual table?
Comment 5 Boris Bokowski CLA 2009-11-26 09:49:34 EST
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 15:31:14 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.