Bug 272668 - Selection issue when switching between Structure Merge Viewers
Summary: Selection issue when switching between Structure Merge Viewers
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 3.5   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-04-17 06:51 EDT by Tomasz Zarna CLA
Modified: 2019-09-06 15:36 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tomasz Zarna CLA 2009-04-17 06:51:35 EDT
With adding an option to switch between available Structure Merge Viewers (bug 220457) an issue with keeping the selection came up. Currently, the bottom part of the Compare Editor, the Content Merge Viewer displays what has been selected in the upper part, the Structure Merge Viewer (if available). If nothing has been selected, full content of the comparison participants is displayed.

Let's use an example here. Consider comparing two Java files. Selecting a node in the Structure Compare pane (a changed method for instance) will result in narrowing the bottom part to that method only. Unselecting the node (clearing selection on the tree) will display full content of the files again.

The problem arises when, after a node has been selected and displayed, the user switches to an alternative structure merge viewer. The new viewer will display its own hierarchical view of changes. The new tree will have no selection, so the bottom part should display full content. However, the bottom part sticks to the previously selected method.

We should consider resetting the viewport of the bottom part on each structure viewer switch.
Comment 1 Eclipse Webmaster CLA 2019-09-06 15:32:07 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 2 Eclipse Webmaster CLA 2019-09-06 15:36:07 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.