diff options
| author | Kenneth Russel <[email protected]> | 2007-03-21 21:06:28 +0000 |
|---|---|---|
| committer | Kenneth Russel <[email protected]> | 2007-03-21 21:06:28 +0000 |
| commit | 0871578761657543a5048b290c7957b08b4625d8 (patch) | |
| tree | c51bda35b11394bb4e77e9405d003905d452c233 /make/jawt-win32.cfg | |
| parent | dccb92d4c54d5c05ead3b7e39540d626a5a3ee96 (diff) | |
Fixed Issue 274: GLException when GLJPanel (initially not visible) is made visible/showing
Investigation revealed that the symptom was similar to what happens
when one tries to create a new OpenGL context against an invalid HDC
on Windows. Discussion with Chris Campbell from the Java 2D team
indicated that in situations where the Java 2D OpenGL pipeline is
using Frame Buffer Objects for its rendering, it is possible that its
internal OpenGL context can be left current to the on-screen drawable,
and it only has a valid device context for the brief period of time
when its OpenGL context was being made current. This means that by the
time JOGL's code got a chance to run, it did not have a valid HDC and
therefore could not create its OpenGL context against it. The
workaround, suggested by Chris, is to forcibly make the Java 2D
context current against its internal "scratch" pbuffer, which can be
done with the internal invokeWithOGLSharedContextCurrent method. Added
this workaround and verified it fixes the problem with the user's test
case. This issue will be fixed in a forthcoming Java SE 6 update
release, hopefully 6u2.
git-svn-id: file:///usr/local/projects/SUN/JOGL/git-svn/svn-server-sync/jogl/trunk@1176 232f8b59-042b-4e1e-8c03-345bb8c30851
Diffstat (limited to 'make/jawt-win32.cfg')
0 files changed, 0 insertions, 0 deletions