JDK-4795382 : GTK+ Look and Feel stock icons could look more like native GTK+ icons
  • Type: Bug
  • Component: client-libs
  • Sub-Component: javax.swing
  • Affected Version: 1.4.2_01,5.0
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic,linux_sun
  • CPU: unknown,x86
  • Submitted: 2002-12-18
  • Updated: 2004-01-21
  • Resolved: 2004-01-21
Related Reports
Duplicate :  
JDK-4869239 - GTK L&F: stock icons need to pick up the same graphics as gtk/gnome stock icons
Duplicate :  
JDK-4912528 - JfileChooser OK and Cancel button Icon are different than Native
Relates :  
JDK-4912613 - Swing's GTK look and feel should be updated to track GTK 2.2
Description
Bring up a Swing JFileChooser, and note the red "X" and green "arrow" in the Cancel and OK buttons.  Bring up gedit's File->Open dialog, and note the red "X" and green "arrow" in the Cancel and OK buttons there.  The stock icon for "X" is thinner and somewhat "italic"; also a paler shade of red.  The stock icon for "arrow" is only lightly green, and fatter.

There are a lot of other stock icons, not checked by the author of this bug.  They could use a quick look too!
Comments
EVALUATION GTK's stock icons are NOT located on the file system (I filed the equivalent of an RFE against GTK for this), instead they are embedded in the gtk library. As we do not link with the library we do not have access to these icons, and because of copyright issues we could not embed them in the JRE, therefor we had to come up with our own similar, yet differenct, icons. I am closing this bug out, if GTK provides the stock icons on the file system, I will recreate a similar bug. ###@###.### 2002-12-18 There are two possible ways to get this information: . dynamically link with GTK to extract this information. This is bad in that if there is some problem in loading the shared library, or some incompatability then the JRE will crash when this happens. . create a subprocess that gets this information and some how reports it back to the JRE. This better isolates the JRE from any problems with getting the information, but it is more problematic in that we have to worry about where this information is stored and what happens when the jre location is shared. ###@###.### 2003-10-03 Looks like we were tracking this issue under another bug number. Closing as a duplicate of that [fixed] bug (4869239). ###@###.### 2004-01-21
03-10-2003