Summary: | [Compare] Have to perform two actions to see diff | ||
---|---|---|---|
Product: | [Eclipse Project] Platform | Reporter: | Scott Rutledge <srutledg> |
Component: | Compare | Assignee: | Andre Weinand <andre_weinand> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | enhancement | ||
Priority: | P3 | CC: | bob, briancort, jcompagner |
Version: | 2.0 | ||
Target Milestone: | 2.1 RC1 | ||
Hardware: | Other | ||
OS: | other | ||
Whiteboard: |
Description
Scott Rutledge
2002-06-13 14:02:02 EDT
*** This bug has been marked as a duplicate of 20106 *** Although the bug this one has been marked as a duplicate of has been fixed, this problem still occurs: the user is forced to double-click the item in Diff view in order to actually see the diff. Reopening. Please bring up the diff for the first file automatically. Do not always bring it up If i am working remote from a cvs server and i do a synchronize i don't want to wait forever when i select a file in the sync view. The synch view first did this (directly compare the selected file) and there where complains about that (which i agree with) The problem is that when you select a file and do compare->with then it should be smart enough to directly open it. The issue for me isn't whether it takes one action or two from the synchronize view. I didn't even know that it was possible to diff the repo's copy with mine. How was I to know that double-clicking would do this (and not update or commit or something dangerous!)? There should be a pop-up (right-click) menu entry for diff'ing. E.g. 'Compare to local copy'. I agree Johan that selecting a file and choosing 'compare with' should always bring up the diff pane right away. Finally, in the Synchronize view, selecting another entry in the top pane should either clear or update the diff pane. These shouldn't be allowed to be inconsistent. Agree with Brian, this stuff is shrouded in mystery. I still don't know how to resolve conflicts in Eclipse. In some files, the "differences merged" (the bottom) menu item would never enable, no matter what I did to the file. I didn't dare try to commit. The last thing I want is to throw away my changes and go back to the repository view. The work cycle I am used to on the command line is: 1) Make changes, 2) Update, 3) Resolve conflicts, 4) Commit. How do you accomplish this in Eclipse? The above questions are meant to be illustrative, not trying to turn this into a newsgroup. ;-} There should be a context menu entry that corresponds to the double click action that shows the diff. This action should be provide in both the compare with and synchronize operations. The compare operation is contributed by compare and the synchronize one is contributed by VCM. Andre can you please take care of the compare operation and then move the bug on the VCM fixed and released for I20030220 As of 2.1, performing Compare With->Latest From HEAD on a single file still does not show the diff automatically, it still requires a second action (selecting the file, which is already selected in the view). |