Posted by ac on Jul 13, 2012; 9:23pm
URL: https://forum.jogamp.org/stuck-in-Processing-with-with-any-JOGL-release-RC6-Mac-tp4025519p4025526.html

@sven:

> It would be better, if you shoot me a message ASAP when things are broken!
> Well, can you point your fingers to the earliest commit/[pre-]release which
> broke things ?

Sorry for the delay in reporting the issue, but I was thinking that maybe I did something wrong and really didn't much time to look at it until now. I will try to locate the earliest commit that triggers the problems.

> This can only happen w/ AWT's GLCanvas.

Yes, the error message is from the tests with AWT. The outcome is not entirely consistent, as sometimes I get the exception and some other times the Processing sketch just doesn't show up without any error. When I switch to NEWT, I only observe the latter behavior

@gouessej

> It would be fine if Processing used the same kind of threading than Ardor3D.

Thanks for the suggestion, I will take a look at the Ardor3D initialization code, maybe it give me some idea of what is wrong. Another tricky thing with this issue is that when I run the OpenGL sketches as a stand-alone application in Eclipse which just depends on the core and opengl Processing packages, it works (with all RCs up to 9). So there must be something related to the way the Processing environment initializes the sketches. but since I cannot reproduce in Eclipse it makes debugging more difficult...

@xerxes

> How do you activate NEWT in processing?

In the PGL.java file in the opengl package, change the value of the toolkit static variable from AWT to NEWT and rebuild.