Posted by ThomasR on Nov 15, 2016; 8:56pm
URL: https://forum.jogamp.org/Java3D-to-Jogamp-Ardor3D-Continuation-tp4036855p4037409.html

Hi Julien,

The first phase of our transition from Java3D requires us to establish that we can use Jogamp's Ardor3D with our
present AWT-Swing based GUIs, so there will be heavyweight-lightweight component mixing in various containers like
JTabbedPane and JSplitPane which can currently cause Java3D to unpredictably crash. I've started with a few Ardor examples and put together a couple of very simpleton examples of my own (you have to start somewhere):

Both examples define a simple method 'getComponet' which returns a heavyweight JoglAwtCanvas from a Scene and a
JoglCanvasRenderer:

SwingTestSplitPane adds a unique canvas to the left and right pane while SwingTestTabPane does the same except for tabs and the container is added to a JFrame.

SwingTestTabPane doesn't work unless only using a single tab, and SwingTestSplitPane sort of works, but is better if the only one canvas is added. Both have problems when resizing the window. I'm wondering if events from the containing Layout manager are perhaps not being handled correctly? Maybe more likely my setup? I've uploading the source code any insight you have I'm sure would be helpful.

Tom

SwingTestSplitPane.java


SwingTestTabPane.java