summaryrefslogtreecommitdiffstats
path: root/doc/userguide
diff options
context:
space:
mode:
authorKenneth Russel <[email protected]>2005-06-09 15:18:44 +0000
committerKenneth Russel <[email protected]>2005-06-09 15:18:44 +0000
commitc33d64db57f3dd66d012c7d0dd27883beb1f2155 (patch)
tree07ae9b72611464f291bbaf15bc8f6f7d64813505 /doc/userguide
parent4f4a4158855d3510f06dbc110d54c2a730ee961c (diff)
Added documentation about -Dsun.java2d.noddraw=true
git-svn-id: file:///usr/local/projects/SUN/JOGL/git-svn/svn-server-sync/jogl/trunk@298 232f8b59-042b-4e1e-8c03-345bb8c30851
Diffstat (limited to 'doc/userguide')
-rw-r--r--doc/userguide/index.html22
1 files changed, 21 insertions, 1 deletions
diff --git a/doc/userguide/index.html b/doc/userguide/index.html
index f25c72d16..1ef37540b 100644
--- a/doc/userguide/index.html
+++ b/doc/userguide/index.html
@@ -526,7 +526,27 @@ The following issues, among others, are outstanding on all platforms:
<P>
-No outstanding issues at this time.
+For correct operation, it is necessary to specify the system property
+<CODE>-Dsun.java2d.noddraw=true</CODE> when running JOGL applications
+on Windows; this system property disables the use of DirectDraw by
+Java2D. There are driver-level incompatibilities between DirectDraw
+and OpenGL which manifest themselves as application crashes, poor
+performance, bad flickering, and other artifacts. This poor behavior
+may exhibit itself when OpenGL and DirectDraw are simply used in the
+same application, not even just in the same window, so disabling
+Java2D's DirectDraw pipeline and forcing it to use its GDI pipeline is
+the only way to work around these issues. Java Web Start applications
+may set this system property by adding the following line to the
+<CODE>&lt;resources&gt;</CODE> section of the JNLP file: <PRE>
+&lt;property name="sun.java2d.noddraw" value="true"/&gt; </PRE>
+
+</P>
+<P>
+
+JOGL currently does not interoperate well with the OpenGL pipeline for
+Java2D available in JDK 5.0 and later. We will address this in a
+future JOGL release and plan to have better interoperability by the
+time JDK 6.0 is shipped.
</P>