444 2010-12-13 16:05:11 +0100 Disable automated termination of NewtCanvasAWT on window close 2015-09-27 03:14:58 +0200 1 1 3 JogAmp Newt awt 1 All all VERIFIED FIXED P4 normal --- 1 karing.martin sgothel FEATURE 2cbab63bd6c230d31b8ae6f1d794ad49bf23bb53 --- oldest_to_newest 717 0 karing.martin 2010-12-13 16:05:11 +0100 The NewtCanvasAWT is automatically destroyed when the parent AWT frame fires a windowClosing event. This is in general a good behavior, yet in some cases a special when something like a "Really close?" window is implemented there must not be a event dispatched that destroys the context. It should be possible to choose if that destruction event is dispatched automatically or not. 729 1 sgothel 2010-12-19 06:57:35 +0100 JOGL/NEWT: Introduce WindowClosingProtocol (solves Bug/Request 444) Similar to JFrame's closing behavior, the following components window closing follow the new WindowClosingProtocol: - GLCanvas - GLJPanel - NEWT Window, GLWindow - NEWT NewtCanvasAWT The implementation obeys either 1) the user value set by this interface, 2) an underlying toolkit set user value (JFrame, ..) 3) or it's default, eg. {@link #DO_NOTHING_ON_CLOSE DO_NOTHING_ON_CLOSE} within an AWT environment. If none of the above determines the operation, this protocol default behavior {@link #DISPOSE_ON_CLOSE DISPOSE_ON_CLOSE} shall be used.