Community
Participate
Working Groups
20111128 build, orion.eclipse.org I was just checking some changes I made to javadoc in the git status page. The results look wrong/corrupt. I went back to make sure the file itself was OK. It is. I checked the side by side compare viewer and the results are correct. So it seems as if the inline compare viewer is getting confused by these changes. I'll attach screenshots to show the results in each viewer.
Created attachment 207670 [details] screenshot of correct results in side by side compare
Created attachment 207671 [details] screenshot of incorrect results in inline viewer
I just realized after taking these screenshots that the problem seems to be that the inline compare viewer on the git status page is comparing the wrong set of files. I had two files in my git status page. commands.js globalCommands.js Clicking on commands.js showed the correct inline compare. Clicking on globalCommands.js seems to be comparing the changes in globalCommands to the content in commands.js Weird...if the files were truly being compared then of course there would be all kinds of diffs. It just appears as if the viewer itself is retrieving the wrong file when showing the diffs. It's grabbing line 22 from commands.js instead of that original ine in globalCommands.js
(In reply to comment #3) > I just realized after taking these screenshots that the problem seems to be > that the inline compare viewer on the git status page is comparing the wrong > set of files. > > I had two files in my git status page. > > commands.js > globalCommands.js > > Clicking on commands.js showed the correct inline compare. > Clicking on globalCommands.js seems to be comparing the changes in > globalCommands to the content in commands.js > > Weird...if the files were truly being compared then of course there would be > all kinds of diffs. It just appears as if the viewer itself is retrieving the > wrong file when showing the diffs. It's grabbing line 22 from commands.js > instead of that original ine in globalCommands.js It might due to my recent change on compare widget. Fixing it now.
fixed with f4a52f6f97b8dc0b7f437c001425984565a0488e.