Closed monkstone closed 11 years ago
The PShader sketches remain sticky even when I get rid of jruby-complete they still won't run:-
Java::JavaLang::RuntimeException
java.lang.NullPointerException
com.jogamp.common.util.awt.AWTEDTExecutor.invoke(AWTEDTExecutor.java:58)
jogamp.opengl.awt.AWTThreadingPlugin.invokeOnOpenGLThread(AWTThreadingPlugin.java:100)
jogamp.opengl.ThreadingImpl.invokeOnOpenGLThread(ThreadingImpl.java:205)
javax.media.opengl.Threading.invokeOnOpenGLThread(Threading.java:172)
javax.media.opengl.Threading.invoke(Threading.java:191)
javax.media.opengl.awt.GLCanvas.display(GLCanvas.java:483)
processing.opengl.PGL.requestDraw(PGL.java:1155)
processing.opengl.PGraphicsOpenGL.requestDraw(PGraphicsOpenGL.java:1602)
processing.core.PApplet.run(PApplet.java:2176)
java.lang.Thread.run(Thread.java:724)
This is now a well reported feature, to run shader sketches (and some others) just use --nojruby flag to use jruby-complete (well since processing-2.1.2)
There is difference in beviour between jruby-complete (default provided) and external jruby when running certain sketches. This has been reported to jruby, but I think it will get very low priority, but it might get fixed as by-product of other changes