Bug 27669 - Jmol's AWT backend gives grey window
Summary: Jmol's AWT backend gives grey window
Status: UNCONFIRMED
Alias: None
Product: classpath
Classification: Unclassified
Component: classpath (show other bugs)
Version: 0.91
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-05-18 19:45 UTC by Egon Willighagen
Modified: 2006-05-18 19:45 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Egon Willighagen 2006-05-18 19:45:06 UTC 
If Jmol 10.2 is started with:

  cacao -Djava.version=1.1 -jar Jmol.jar

then it shows a grey screen. Somewhere last autumn I spoke with someone on #classpath about this, and he thought it could be caused by the fact that Jmol assumes a RGB feature, while Classpath returns a RGBA, in effect incorrectly setting the transparency, giving the grey output. I do remember trying some workarounds for that, but it never worked.

The involved Jmol code looks like:

ColorModel colorModelRGB;
  ImageConsumer ic;

  Awt3D(Component component) {
    this.component = component;
    colorModelRGB = Toolkit.getDefaultToolkit().getColorModel();
  }

See:
 http://svn.sourceforge.net/viewcvs.cgi/jmol/branches/v10_2/Jmol/src/org/jmol/g3d/Awt3D.java?view=log

If the java.version parameter is not given, Jmol uses a Swing backend, which works properly. The Sun JVM works properly in AWT mode, so there seems to be some incompatibility.

Egon