This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
To workaround the Beans.isDesignTime() issue described here: http://www.netbeans.org/issues/show_bug.cgi?id=127935 NetBeans should use sun.awt.AppContext to store a designtime flag in the scope of the form designer components additional to the VM-global Beans designtime flag. GUI components like GLCanvas and GLJPanel of the JOGL API are forced to detect design mode to render properly. Detecting it with Beans.isDesignTime() breaks all of those components when used in a IDE plugin. Right now, this can't be solved from the GUI component point of view.
I agree with you that Beans.isDesignTime() is not usable. But I'm afraid this can't be solved from the GUI builder point of view either. We cannot use AppContext for the components in the GUI designer because the visualized components are placed in the same AWT hierarchy and use the same event queue thread as the NetBeans IDE. I don't see how it could be possible to separate. If you do, please tell us.
Ok I understand, I got a hint from the JOGL author that AppContext could be the solution to this issue but it seems to be clear that this is also not the way to go :/
Closing as 'will not fix' (according to the last comments).