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

Bug 128462

Summary:	[History View] Compare Editor opening prefs
Product:	[Eclipse Project] Platform	Reporter:	Bogdan Gheorghe <gheorghe>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	Keywords:	helpwanted
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Bogdan Gheorghe

2006-02-17 14:43:54 EST

From Bug 125857 - here are some issues with our compare editor opening strategy (which currently always seeks to reuse an editor given that it's not dirty):

<snip>

I now also have to do more interactions than before and think up front: before
I could open two compare editors via
1. select file A.java, Compare With > Revision...
2. select file B.java, Compare With > Revision...

Now I must not forget that step two changes the input of the new history view
i.e. I have to first pin the view, or later again go back to the Package
Explorer and select A.java (the history view does not have a history itself
(e.g. a 'Back' button). Interesting will also be how the compare editors behave
once bug 125861 will be fixed i.e. will two different History views reuse the
same compare editor and waste one that I'm still interested in since I opened
it from a different (pinned) History view?

Comment 1 Michael Valenta

2006-09-14 11:06:46 EDT

We do not plan on adressing this issue in 3.3.

Comment 2 Eclipse Webmaster

2019-09-06 16:17:34 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 3 Eclipse Genie

2021-10-27 02:59:59 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. 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.