Eclipse, Proclipsing, Opengl rendering trouble

Kobby

Eclipse, Proclipsing, Opengl rendering trouble

in Integration and Hardware • 1 year ago

Hey all,

I recently asked a question trying to figure out how to get fullscreen using proclipsing in eclipse. The solution I got totally works, except when I try to use the PApplet.OPENGL as a renderer.

using this :

size(400,400, PApplet.OPENGL);
frame.setResizable(true);
size(screenWidth, screenHeight, PApplet.OPENGL);
frame.setResizable(false);
background(255, 0,0);

gives me this :

Thread [Animation Thread] (Suspended (exception GLException))

MacOSXOnscreenGLContext(GLContextImpl).destroy() line: 176 [local variables unavailable]

PGraphicsOpenGL.allocate() line: 294

PGraphicsOpenGL(PGraphics3D).setSize(int, int) line: 326

HarleyTwitterFeed(PApplet).resizeRenderer(int, int) line: 1060

HarleyTwitterFeed(PApplet).size(int, int, String, String) line: 1140

HarleyTwitterFeed(PApplet).size(int, int, String) line: 1106

HarleyTwitterFeed.setup() line: 11

HarleyTwitterFeed(PApplet).handleDraw() line: 1608

HarleyTwitterFeed(PApplet).run() line: 1530

Thread.run() line: 680 [local variables unavailable]

Using it in one of the 2 just gives me a blank screen that doesnt render anything. Any one know of a way around this?

Replies(6)

calsign

Re: Eclipse, Proclipsing, Opengl rendering trouble

1 year ago

It's probably because you're initializing OpenGL twice... can you remove the first call to size()?
Alternatively, can you use some form of resize() (yes, this is a function) instead of size()?

On a separate note, I'm pretty sure that you're extending a PApplet... so why do you need to prefix OPENGL with PApplet?

Kobby

Re: Eclipse, Proclipsing, Opengl rendering trouble

1 year ago

In answer to your separate note, yes PApplet.OPENGL is totally redundant and didnt need to be set up that way.

the problem, however is that I can't remove the first size call, that will work in running code but when I export with the the project to an app I get an error that nags at me to use numerical values. however if I keep the first one in there, the app exports fine, if i'm not using OpenGL.

using the resize function is giving me some weird results, it looks almost as if it resizes the frame but not the graphics context. I get a screen where the background color is the dimension of the original size call but the rest of the frame is made of blurred pixels from one of the tabs in my google chrome window, so something entirely different from the actual app itself.

It seems like this problem is with the Proclipsing exporter because the code runs fine in eclipse just doesn't want to export.

Maybe this is the wrong forum for this post haha.

PhiLho

Re: Eclipse, Proclipsing, Opengl rendering trouble

1 year ago

I haven't tried, but from what I read in the code, you should make a first call without renderer parameter (thus using the default, JAVA2D one), and then call the second one with the OPENGL parameter, it will create a new underlying PGraphics.

Kobby

Re: Eclipse, Proclipsing, Opengl rendering trouble

1 year ago

Hmm see that gives me a strange situation where there are no errors but no graphics either.

just a black screen.

This is what my code looks like. I never get a rectangle.

public void setup() {
size(400,400);
frame.setResizable(true);
size(screenWidth, screenHeight, OPENGL);
frame.setResizable(false);
background(255, 0,0);
}
public void draw() {
fill(255);
rect(0,0,200,200);
}
public static void main(String _args[]) {
PApplet.main(new String[] { "--present", "--hide-stop", harleytwitterfeed.HarleyTwitterFeed.class.getName() });
}

calsign

Re: Eclipse, Proclipsing, Opengl rendering trouble

1 year ago

You're creating it in present mode? I'm guessing that that's what the first argument to PApplet.main() means... I'm curious if that could be the source of the problem...

Kobby

Re: Eclipse, Proclipsing, Opengl rendering trouble

1 year ago

taking it out of present mode just gives me the gray default screen. but still no rectangle or red background.

I'm wondering at this point if the problem is with the exporter and if i should focus on the Proclipsing exporter, or not using it. I dont have to do this hack at all if i'm not using the proclipsing eclipse plugin so I may end up just rebuilding this project the old eclipse way and set up my own build path with the libraries.

Top Reply