Bug 279

---- Reported by dmgaskin 2007-02-25 05:51:01 ----

package de.gaskin.jogl.bugs;

import javax.media.opengl.GLJPanel;

class DMGJOGLhttps://jogl.dev.java.net/bugs/show_bug.cgi?id=2 {
   public static void main(String[] args) {
      GLJPanel panel = new GLJPanel();
      panel.setAutoSwapBufferMode(false);
   }
}


Exception in thread "main" java.lang.NullPointerException
        at javax.media.opengl.GLJPanel.setAutoSwapBufferMode(GLJPanel.java:758)
        at de.gaskin.jogl.bugs.DMGJOGLhttps://jogl.dev.java.net/bugs/show_bug.cgi?id=2.main(DMGJOGLhttps://jogl.dev.java.net/bugs/show_bug.cgi?id=2.java:8)

Jogl VERSION

jogl-1.1.0-rc3-windows-i586



---- Additional Comments From kbr 2007-02-27 14:20:02 ----

This can be worked around by calling this method in the init() method of your
GLEventListener. Other methods on the GLJPanel have similar restrictions in the
current implementation. Downgrading from a P1.



---- Additional Comments From kbr 2008-03-30 16:40:04 ----

This issue turned up with NASA World Wind Java as well as with this
bug report.

The current situation is that GLJPanel.setAutoSwapBufferMode() and
GLJPanel.swapBuffers() have no effect due to how the Swing-compatible
GLJPanel works, and due to the fact that the backing OpenGL drawables
for the GLJPanel are always single-buffered.

Therefore there is no adverse effect to current applications to simply
making setAutoSwapBufferMode and swapBuffers no-ops, and returning
"true" from getAutoSwapBufferMode (although the latter is a change in
behavior, it reflects the current reality).




--- Bug imported by sgothel@jausoft.com 2010-03-24 07:50 EDT  ---

This bug was previously known as _bug_ 279 at https://jogl.dev.java.net/bugs/show_bug.cgi?id=279