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

Bug 101649

Summary:	[Viewers] non-VIRTUAL TableViewer.getRawChildren() should not reject any IStructuredContentProvider
Product:	[Eclipse Project] Platform	Reporter:	Jörg von Frantzius <jfrantzius>
Component:	UI	Assignee:	Platform UI Triaged <platform-ui-triaged>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.1
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Jörg von Frantzius

2005-06-24 10:41:46 EDT

TableViewer.getRawChildren() contains an assertion that the ContentProvider in
place must not be an ILazyContentProvider. Maybe I didn't understand something
fundamental here, but I can't see why I must not implement an IContentProvider
that works both with VIRTUAL and non-VIRTUAL TablesViewers?

Please remove this assertion or explain (also in the JavaDoc) why an
IContentProvider implementation must not work both with VIRTUAL and normal
TableViewers. 

If there is a reason, TableViewer.setContentProvider() should already reject the
ILazyContentProvider.

Comment 1 Tod Creasey

2005-06-24 10:50:23 EDT

Because we have no way of knowing how to populate the lazy content provider if
you are not virtual - i.e. there is no callabck from SWT to tell us what to ask for.

Comment 2 Jörg von Frantzius

2005-06-27 07:18:02 EDT

What if that ILazyContentProvider also implements IStructuredContentProvider? 

What  methods does a class have *less* when it implements an additional
interface, i.e. ILazyContentProvider?

Comment 3 Tod Creasey

2005-06-27 07:46:20 EDT

Point taken on that - we should protect for both cases.

Comment 4 Boris Bokowski

2009-11-26 09:51:00 EST

Hitesh is now responsible for watching bugs in the [Viewers] component area.

Comment 5 Eclipse Webmaster

2019-09-06 16:11:52 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.

Comment 6 Eclipse Genie

2021-12-02 12:42:10 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.