Posted by BrickFarmer on Nov 30, 2010; 9:47am
URL: https://forum.jogamp.org/re-NEWT-Threading-Overview-tp1991718.html

So currently my project uses many GLCanvas instances, but they all share a common context (I think I originally did this due to issues with textures not being shared).  Anyway I'm really interested to read about the possibilities of using NEWT & Swing together! that's really great!  So now I'm wondering how this would work in practice...

Is there a similar concept of a shared context so that the textures bound to the context are available to all the NEWT Displays (Display is the right word? or are they still called canvases - still trying to get my head around what NEWT is...)

Currently I have a base class that encapsulates my GLCanvas.  This consumes a few common keyboard and mouse events.  The owning container (dialog or frame) also attaches a listener so it also has a chance to process these same, and other events that the child wasn't interested in.  I'm wondering how a decoupled EDT will work in this case.  
is it still possible that as I switch focus between my multiple canvas's I'm going to receive my events as before?  
Does a parent container have a chance to 'add a listener' to the EDT?
I read something about 1 EDT per Display?  whereas currently swing is a single EDT for the whole app and all my canvases.  So my app currently has around 20 canvas's, does that mean now 20 EDT threads?  Does it also mean 20 rendering threads?

Anyway great to see some doku appearing for NEWT :)

PS cork=peter=brickfarmer.  I had some issues setting up my account originally