Another weird behaviour.
I'm trying to have multiple threads that render to the same surface.
So I'm creating a single EGLSurface form the SurfaceHolder and then an
EGLContext for each thread.
Each thread calls the eglMakeCurrent function passing the eglSurface
(for both read/write) and its own
Soory, the documentation link is
http://www.khronos.org/opengles/sdk/1.1/docs/man/eglMakeCurrent.xml
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
Never ending story.
Is it possible that creating multiple EGLSurfaces form the same
SurfaceHolder gives problems even if only ONE of this surface is
current on ONE thread with ONE context?!?
I can not belive to have so many issues with the OpenGL|ES binding on
the Android platform.
It would be
3 matches
Mail list logo
