Community
Participate
Working Groups
Build Identifier: Version: 3.6.2 M20110210-1200 Selecting 2 files and using "Compare With" --> "Each other" the background of the displayed file areas are back, also the markers at the boarders. This symtome was also seen with other like: .log files with Aptana Studio Reproducible: Always Steps to Reproduce: 1.select two files 2. use "Compare with" --> "Each other"
Created attachment 198324 [details] faulty compare with example
Created attachment 198328 [details] Text Compare This PNG shows the "Text Compare" display with line numbering and markers at the right boarder. A chnage with "preference" doesn't work, as it's possible to change attributes (background, selected line color, etc) with normal File view (Opened with "Text Editor")
Let me make sure I understand the problem correctly: the black background color is not set by you in preferences? If you go to Window -> Preferences -> General -> Appearance -> Colors and Fonts and hit "Restore Defaults" button the background and borders are still black? The same problem doesn't happen when you open the same files in normal editor?
(In reply to comment #3) > Let me make sure I understand the problem correctly: the black background color > is not set by you in preferences? If you go to Window -> Preferences -> General > -> Appearance -> Colors and Fonts and hit "Restore Defaults" button the > background and borders are still black? > The same problem doesn't happen when you open the same files in normal editor? Yes! All points right, description as it is! Because of that situation I went back to 3.4.2 which hasn't that problem!
I have this problem exactly as described with only eclipse helios. However if I start the same eclipse version with a new project in a new workspace I do not see the problem so it is related to some "junk" in the existing workspace metadata. However I cannot figure out what that junk is. I have a HUGE set of changes to submit to subversion and I'm going to have to use a text diff viewer to do it, then destroy and recreate my workspace. I'll keep a copy in case someone who knows a little bit about workspaces wants to help out. wcn
neandr, are you able to reproduce the issue after you have created a new workspace and a new project? Just like Wendell did in his comment above.
Created attachment 199627 [details] Another example of the Bug in Eclipse Indigo
I'm getting this bug too in Indigo (eclipse.buildId=I20110613-1736) on OSX. See attached screenshot: https://bugs.eclipse.org/bugs/attachment.cgi?id=199627 I did not change my font and color settings, but I went through the hierarchy and clicked "Restore Defaults" then "Apply". I did set and reset to make sure that it takes. One thing: I'm not sure, but I *might* have installed Aptana in this version of Eclipse.
(In reply to comment #6) > neandr, are you able to reproduce the issue after you have created a new > workspace and a new project? Just like Wendell did in his comment above. Had to move back to working solution with E 3.4.2. Could not move the different projects over to a new Eclipse version and defining new profile. Sorry, just time constrains. Günter
I had the same problem after switch from eclipse helios to eclipse indigo. after removing this file: workspace/.metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.compare.prefs and restarting my workspace problem has gone. The mentioned file was NOT created when we I made a brand new workspace in eclipse indigo.
Created attachment 199771 [details] org.eclipse.compare.prefs causing the problem file mentioned in Comment 10
Thank you so much Adam, that fixed the problem! There is still a bug that needs fixing, but that's a legit workaround. Here are the commands I entered in terminal on OSX: cd [workspace] rm .metadata/.plugins/org.eclipse.core.runtime/.settings/org.eclipse.compare.prefs Interestingly, the changes that I had made to compare font finally showed through after I deleted that file.
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. If the bug is still relevant, please remove the "stalebug" whiteboard tag.
