Posted by gouessej on Jun 16, 2015; 9:44am
URL: https://forum.jogamp.org/Resize-problem-tp4034612p4034710.html

It's not intentional. You can disable the double buffering. In my humble opinion, you should make it work without interfering with the rendering, by rendering even when the scene isn't moving. Then, when it works, you should test with other canvases too in order to ensure that the problem comes from your own code rather than mine. After that, use your code to stop the rendering when the scene doesn't move.

JoglSwingCanvas is the least performant JogAmp's Ardor3D canvas. I think that your main concern is the poor AWT implementation under Mac OS X, both in Apple and Oracle JREs.

Rendering anew only when it is necessary can help to decrease the energy consumption but it is tricky to implement just right. I don't advise you to do so except for often modified very large meshes. I'm not sure it's worth the efforts in the general case.