Posted by William Bittle on Apr 29, 2012; 6:56pm
URL: https://forum.jogamp.org/NewtCanvasAWT-Questions-tp3949030.html

Just a few questions about the NewtCanvasAWT class.

I've been having some threading issues using Swing and GLCanvas as described on the jogamp site.  So I decided to bite the bullet and move to NEWT, specifically using the NewtCanvasAWT class (which wasn't that bad).

On to the questions:
1. Is the NewtCanvasAWT intended for the purpose of having NEWT performance while retaining the UI components of AWT/Swing?  (This is the case from what I understand).  Is this a temporary compatibility layer?  What are the downsides of this vs. GLCanvas?
2.  Having already tried this (with great results as far as the threading issue), I do have one issue.  When the user clicks the GL rendered area and holds the button, the mouse cursor is changed via NewtCanvasAWT.setCursor(Cursor.getPredefinedCursor(Cursor.MOVE_CURSOR)).  This works well, however, as the mouse is moved the cursor flickers back and forth between the MOVE_CURSOR and the default cursor.  It does not flicker while stationary.  Here is an extremely poor quality video illustrating the problem: Cursor Problem
3.  I'm getting "Detected screen size 1280x1024" printed to the console.  Is there anyway to stop this?  Not sure where its coming from, but it only showed up after I started using GLWindow/NewtCanvasAWT.

Thanks William