FAQ
Cover
\
Build
\
Source
\
Bugs
\
Reference
\
Libraries
\
Tools
The bugs database has moved
here
.
Bug 164 : OPENGL + noLoop() no run
Last modified: 2006-08-02 19:20
P
roject:
processing
trash
Version:
unspecified
Co
m
ponent:
android
book
core
libraries
pde
reference
tools
web
Status:
RESOLVED
Resolution:
FIXED -
Pr
i
ority:
P4
Severity:
normal
Platform
All
O
S:
All
Windows
Mac OS
Linux
Other
Reporter:
analogAI
Assigned To:
fry
Attachment
Type
Created
Size
Actions
Description
: Opened: 2005-09-28 19:48
Seems to be a bug when using OPENGL in combination with noLoop(). I'm using
Win2k Processing 0091 Beta.
the bug described previosly here:
http://processing.org/discourse/yabb_beta/YaBB.cgi?board=SoftwareBugs;action=display;num=1115330568;start=3#3
It gives an InterruptedException:
java.lang.RuntimeException: java.lang.InterruptedException
at processing.opengl.PGraphicsGL.requestDisplay(PGraphicsGL.java:166)
at processing.core.PApplet.run(PApplet.java:951)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.InterruptedException
at java.lang.Object.wait(Native Method)
at java.lang.Object.wait(Unknown Source)
at java.awt.EventQueue.invokeAndWait(Unknown Source)
at
net.java.games.jogl.GLCanvas.maybeDoSingleThreadedWorkaround(GLCanvas.java:220)
at net.java.games.jogl.GLCanvas.display(GLCanvas.java:75)
at processing.opengl.PGraphicsGL.requestDisplay(PGraphicsGL.java:157)
... 2 more
working code:
//---
import processing.opengl.*;
void setup()
{
size(200, 200, OPENGL);
//noLoop();
}
void draw(){
translate(width/2,height/2,0);
rotateX(TWO_PI*10/360);
rotateY(TWO_PI*20/360);
rotateZ(TWO_PI*20/360);
box(50,50,50);
}
//---
non-working code:
//---
import processing.opengl.*;
void setup()
{
size(200, 200, OPENGL);
noLoop();
}
void draw(){
translate(width/2,height/2,0);
rotateX(TWO_PI*10/360);
rotateY(TWO_PI*20/360);
rotateZ(TWO_PI*20/360);
box(50,50,50);
}
//---
Additional Comment
#1 From fry 2005-10-04 15:14
this may actually be fixed with the newer jogl that will arrive with rev 93, will have to
check.
Additional Comment
#2 From fry 2005-10-16 10:21
nope, not fixed.. will have to track down what's going on. that threading
stuff is pretty nasty and tied to lots of other things..
Additional Comment
#3 From fry 2006-08-02 19:20
now fixed for 0116.