Community
Participate
Working Groups
I200405282000 When running Eclipse under KDE 3.2.2, using kcontrol/krdb to apply KDE colours to Gtk+-2.0 applications, the code assist popup uses colours which make it difficult to tell which item is selected in the list. Furthermore, the colours do not seem to make sense with the rest of the colour scheme. This may be a KDE issue, as there seem to be other usability problems with krdb. For example, see http://bugs.kde.org/show_bug.cgi?id=82619 . However, since these colours seem quite shockingly strange, I wonder if maybe Eclipse is not using the correct colours at all.
Created attachment 11344 [details] Screenshot showing the code assist colours
Also see some discussion in bug 49548.
This is a bigger issue than just colours on KDE. It generally breaks selection highlighting on high contrast on Windows as well. The content assist has two colour settings: Completion proposal foreground and background. The issue is that a list also has two other colour pairs 1) Focus selected foreground and background 2) Non focus selected foreground and background If you are not using system colours to set these values then the mix with the two settings will cause problems. For example on Windows 1) Set colours to High Contrast 2) Invoke code assist. White background with black foreground (opoosite of what you want). No focus and focus Selected item is black - should be black and purple to tell the difference 3) Set the colours in the Code Assist preference page to be white on black (attempt to emulate the system settings) 4) Invoke code assist. Non focus select matches background so you cannot see the default selection until you give focus to the widget when it becomes purple. We would recommend not setting these colours at all or if you do modify the system color.
*** Bug 65998 has been marked as a duplicate of this bug. ***
*** Bug 70042 has been marked as a duplicate of this bug. ***
*** Bug 69278 has been marked as a duplicate of this bug. ***
*** Bug 70859 has been marked as a duplicate of this bug. ***
This bug is a duplicate of bug 66815. The issue was in kcontrol/krdb which is fixed in KDE 3.2.3 and later. *** This bug has been marked as a duplicate of 66815 ***
*** Bug 78787 has been marked as a duplicate of this bug. ***