Quick question: How to destroy a PApplet without terminating the entire JVM?

Integration and Hardware

markmarij..

Quick question: How to destroy a PApplet without terminating the entire JVM?

in Integration and Hardware • 2 years ago

I launch processing sketches from MAX/MSP & Matlab.

To do this, I instantiate a Frame (AWT) and add the PApplet as a component.

Then I init() and start() the applet, make the frame visible, and do a redraw().

Now - how do I destroy the PApplet?

Calling destory() calls stop() which calls exit at some point and terminates MAX/MSP or Matlab.

There these other methods like dispose() and delete() - but I have no clue what they are doing.

Please help me out, as I might be creating and destroying a lots of processing sketches!

Thanks!

public static void show(PApplet aSketch)
{ sketch = aSketch;
frame = new Frame(sketch.toString());
/* do layout stuff */
frame.add(sketch);
/* do frame stuff */
frame.addWindowListener(new WindowAdapter(){
public void windowClosing(WindowEvent we){
frame.dispose();
frame = null;
/* HOW TO DESTROY THE SKETCH HERE??? */
}
});
//initialize applet, start everything...
sketch.init();
sketch.start();
frame.setVisible(true);
sketch.redraw();
}

Replies(4)

PhiLho

Re: Quick question: How to destroy a PApplet without terminating the entire JVM?

2 years ago

More exactly, destroy() calls exit() which in turn calls exit2(), doing the System.exit(0).
You can try and override exit2() in your sketches to avoid this call. Mmm, it is package protected, so hard to override.
Perhaps you should override exit() itself.

rbrauer

Re: Quick question: How to destroy a PApplet without terminating the entire JVM?

2 years ago

Cant you just call sketch.stop()?

PhiLho

Re: Re: Quick question: How to destroy a PApplet without terminating the entire JVM?

2 years ago

In recent versions of Processing, it will just pause the animation thread.

markmarij..

Re: Quick question: How to destroy a PApplet without terminating the entire JVM?

2 years ago

I thought I already responded??

Anyway.. phi.lo pointed me in the right direction. I delved into processings source code and discovered the following:

- stop() only pauses the thread

- destroy() calls exit(), which has different scenarios, but each of them calls dispose() to free resources and exit2() to exit the application.

So nothing needs to be overriden - you can simply call "dispose()" if you want to free the resources used by the PApplet.

Top Reply