RE: [gl4java-usergroup] moving to jogl

[Combe, C. <C....@na...>]

b.t.w., i didn't mean to imply that the existence of this bug was a sign of
incompetence on behalf of the developers - just that I could try to fix it
myself even though I'm not the most experienced of programmers. In general I
would like to be more involved with the developemnt of the java/Gl binding
but tend to think that not knowing C would limit my usefulness. 
I will look at the area of code you highlighted when I start working with
JoGL,
cheers,
colin
-----Original Message-----
From: Kenneth B. Russell
To: Colin Combe
Cc: gl4...@li...
Sent: 6/16/03 4:01 PM
Subject: Re: [gl4java-usergroup] moving to jogl


> However, does the fact that :
> >The OpenGL context handling and 
> >interaction with the window system has been
> >completely redesigned and is in fact now written in Java instead
> >of in C. 
> mean that a reasonably competent java programmer might be able to fix
it? 
> What exactly is the problem?

I just checked the source code and it looks like we planned ahead
for this but just haven't stress tested it yet.

See roughly line 156 in
src/net/java/games/jogl/impl/windows/WindowsOnscreenGLContext.java
and roughly line 142 in
src/net/java/games/jogl/impl/x11/X11OnscreenGLContext.java, in
particular the checking for JAWT_LOCK_SURFACE_CHANGED. I don't
know whether that will be sufficient; in particular I think if a
canvas is being animated and it's removed from its parent it will
probably start returning JAWT_LOCK_ERROR, which will cause the
GLException a few lines earlier to be thrown.

-Ken