Bug 240298

Summary: [Dialogs] History in the "Compare with" dialog
Product: [Eclipse Project] Platform Reporter: Aleksandra Wozniak <aleksandra.k.wozniak>
Component: CompareAssignee: Platform-Compare-Inbox <platform-compare-inbox>
Status: ASSIGNED --- QA Contact:
Severity: enhancement    
Priority: P3 CC: aleksandra.k.wozniak, markus.kell.r, tomasz.zarna
Version: 3.4   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard:
Bug Depends on: 241088, 73923, 239959, 244623    
Bug Blocks: 224562    
Attachments:
Description Flags
History for each "file" in "Compare With" dialog
none
patch #2
none
patch #3 none

Description Aleksandra Wozniak CLA 2008-07-10 04:48:26 EDT
As mentioned in bug 224562 it would be convinient to have a history for each "file" in the "Compare With" dialog.
Comment 1 Aleksandra Wozniak CLA 2008-07-14 07:45:19 EDT
Created attachment 107318 [details]
History for each "file" in "Compare With" dialog

The patch from the "bug_20080710_CompreWithDialog" branch.
Comment 2 Tomasz Zarna CLA 2008-07-14 09:27:18 EDT
The patch is not applicable in the provided form"
* CompareWithOtherResourceDialog already exists in the branch, cannot add it
* the same with CompareWithOtherResourceAction
* removing the org.eclipse.compare.internal.Messages.java class is addressed by bug 240294
Comment 3 Tomasz Zarna CLA 2008-08-19 10:28:48 EDT
Ola, this patch does not apply against HEAD. Could you please update it?
Comment 4 Aleksandra Wozniak CLA 2008-08-25 05:12:14 EDT
Created attachment 110784 [details]
patch #2
Comment 5 Aleksandra Wozniak CLA 2008-08-28 08:44:55 EDT
Created attachment 111198 [details]
patch #3

Based on latest changes from bug 241088 and bug 73923.
Comment 6 Tomasz Zarna CLA 2008-09-01 06:20:41 EDT
It appears that history entries doesn't show up in drop down lists. Did I miss anything?
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:13:12 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.