Is the EventDispatchThread being used somewhere in the initialization of JOGL and/or Java3D in pre11 where it wasn't
before in pre9? My assumption has been, and perhaps this is incorrect, that we could start Java3D and have it render off the swing thread so as not to freeze up the gui. My application is behaving a little different, working very well, but also seems slower, when I moved from pre9 to pre11.
Thanks for your reply. It's a damn waitCursor problem, such a PITA in Swing. This used to work:
(1) on EDT set cursor to wait
(2) start a SwingWorker do some heavy processing, start Java3D, render
(3) done back on EDT set cursor to default. Show the results in a new Window
But if Java3D/JOGL perform operation on the EDT, the wait cursor might get interrupted which is
happening now, some subtle change from pre9 to pre11 has shown me I can't do it this way. So
it's my problem. How do you handle this sort of thing?