Posted by
Sven Gothel on
Mar 28, 2012; 11:35pm
URL: https://forum.jogamp.org/Problem-when-using-an-external-context-tp3851637p3866312.html
On 03/29/2012 01:13 AM, herve [via jogamp] wrote:
>
>
> arghh you may be right. When you say "later", does it mean that we have to
> wait a little in the Java side for the context to be available ? It's true
> that we called the createExternalGLContext method in Java as soon as
> possible in the Java side (not because it was really necessary for us
> though, just because we did not think about it as it worked with JOGL
> 1.1.1).
>
> However thanks for your advice, but also for your work on this very good
> API.
Thank you :)
We currently use GLDrawableFactory.createExternalGLContext()
in GLJPanel for it's Java2D-OpenGL-Backend and in the SWT unit test
'TestSWTEclipseGLCanvas01GLn'.
We currently use GLDrawableFactory.createExternalGLDrawable()
only in GLJPanel right now ..
Both work use cases work pretty well, having ensured that at the time
they are called (fetching the current context and drawable from JOGL),
the 'external' entity has set them current.
If you like, I would appreciate more unit tests on this.
You could simply create the 'external' context w/ JOGL itself
and hook it up with with the above mentioned calls and using them.
Then we would merge your unit test code and it will be maintained well.
The problem w/ your current negative experience is that we have no way
to validate your description and reproduce it, since we have no source code.
Kind regards, Sven