Bruce Schubert
|
Posted: November 24, 2009 13:51 by Bruce Schubert
|
|
Hi, I added the OpenGL Capabilities Viewer to my RCP-suite project which conveniently added the viewer to my application's Tools menu. Cool. The viewer seems to work just fine, until I close it. When I close it, I lose the contents of my NASA WorldWind GLCanvas-based window -- it goes black and says "canvas0". Now, I don't need the Capabilities Viewer in my app, so I removed it from the suite's library list. But issue is a curiosity. Any ideas? My WorldWind-based module only has dependencies the JOGL and GlueGen modules. Does it need others for compatibility with the Capabilities Viewer? -- Bruce |
Problem closing the OpenGL Capabilities Viewer
2 posts
Replies: 1 - Last Post: November 24, 2009 18:02
by: Michael Bien
by: Michael Bien
showing 1 - 2 of 2
Michael Bien
|
Posted: November 24, 2009 18:02 by Michael Bien
|
|
yes... its a long story and a bad hack. the root of the problem is: the Form Designer has some issues with native libs. This motivated the jogl devs to check Beans.isDesignTime() and render a black dummy window in case jogl detects its inside the gui builder. ...But Beans.isDesignTime is static and even worse, Beans is a class in the boot classpath (can't be reloaded in another classloader). This means as soon the form designer starts (which sets Beans.designtime(true)) all jogl components would render a black screen.... The capabilities viewer was designed to run in the IDE (with the danger to conflict with the form designer) thats why it sets Beans.setDesignTime(false) on open and back to true on close. Since JOGL is now a community effort we will probably remove the hack entirely (from JOGL) and also drop the form designer support of the NB GL Pack. If you want to use the capabilities viewer in your rcp app the quickest fix would be to uncomment all Beans.* calls. |
Replies: 1 - Last Post: November 24, 2009 18:02
by: Michael Bien
by: Michael Bien
