Hi, I also have a beef with with the way the buffer swapping
is done in JOGL.  It does the swap for you, after it calles
GLEventListener.display()!  This has been problematic for
me to - it broke my XOR graphics update system on the
Sun computers (which JOGL doesnt seem to work well on right now anyway) because the hardware there does a pointer swap rather than a buffer copy for glSwap().  So my code wrote onto the front buffer for an XOR updates on the Suns.  Also I would like to be able to defeat a swap entirly if my code can determine there was really no reason to do an update.  Did you subclass your own GLCanvas?

I have to chime in here and agree. It causes me significant problems with some client code I've been working on where I need to have more fine grained control over when the buffer swaps and the solution in JOGL isn't quite ideal. As I started digging through the JOGL source I discovered that it doesn't HAVE to be this way, but is more a convenience thing the way it is implemented.

Not sure the current design is the best for applications that need more swaps than one per frame.

Hi Sean,

Here's a rundown of what I changed.

CamerGLCanvas - I had to change GLCanvas because it used a factory class to create its context.  Since it's final I can't override anything.  It uses CameraGLContextFactory and CameraGLContextHelper.

CameraGLContextFactory - I changed this one so it would return CameraWindowsGLContextFactory as the factory class.

CameraGLContextHelper - This one is because GLContextHelper has package scope.

CameraOnscreenGLContext - This is the one that actually controls the SwapBuffer call.  It extends WindowsOnscreenGLContext.  I used the NoAutoRedrawMode boolean as the logic switch.  This probably is an inappropriate use of this boolean but it works for now.

CameraWindowsGLContextFactory - This returns an instance of CameraOnscreenGLContext.

As a temporary solution, I directly instantiate CameraGLCanvas instead of using a factory.  i.e. glCanvas = new CameraGLCanvas(glCapabilities, null, null);

I think that's it.
Gregg

PS:  I emailed the code to you.