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.
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.