Bug 183455 - [Viewers] Duplicate-Instances in Viewers problems parts with potential problems including wrong item comparison
Summary: [Viewers] Duplicate-Instances in Viewers problems parts with potential proble...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.3   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-04-20 16:12 EDT by Thomas Schindl CLA
Modified: 2019-09-06 16:04 EDT (History)
0 users

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 Thomas Schindl CLA 2007-04-20 16:12:11 EDT 
Questionable Code-Parts:
- AbstractTreeViewer#itemExists()
- CheckedTreeViewer in general because and because TreeViewer supports it
- StructuredViewer#associate()
- TreeViewer#handleTreeExpand() don't we have to pass the TreePath to uniquely 
  identify which item is expanded?
- ILazyTreeContentProvider don't we have to pass the TreePath?
- ViewerDropAdapter only the model object is not good enough for TreeViewer with 
  multiple same instances.

This is only a list I came up in the last minutes. We should look closer to those parts and see if the current implementation is correct or not I only wanted to log the code parts so that they are not forgotten.
Comment 1 Eclipse Webmaster CLA 2007-07-29 09:22:26 EDT 
Changing OS from Mac OS to Mac OS X as per bug 185991
Comment 2 Boris Bokowski CLA 2009-11-26 09:48:24 EST 
Hitesh is now responsible for watching bugs in the [Viewers] component area.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:04:32 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.