Yeah, I understood your point. Manual updating of viewport and
drawable seems to be needed in this case unless we change
EGL specificiation. Thanks
On Tue, Aug 23, 2016 at 05:51:23PM +0100, Emil Velikov wrote:
> On 23 August 2016 at 17:36, Dongwon Kim wrote:
> > I read that part in egl specificat
On 23 August 2016 at 17:36, Dongwon Kim wrote:
> I read that part in egl specification as well but I wasn't sure
> if this statement covers the case when the context is unbound via
> eglMakeCurrent call with NULL context then it is made current again.
> The problem I saw was when the context is ma
I read that part in egl specification as well but I wasn't sure
if this statement covers the case when the context is unbound via
eglMakeCurrent call with NULL context then it is made current again.
The problem I saw was when the context is made current again especially
with a new surface with d
On 15 August 2016 at 23:58, Dongwon Kim wrote:
> 'ViewportInitialized' flag in gl_context has to be reset to '0'
> when the current context is unbound via a eglMakeCurrent call with
> all of 'NULL' resources (surfaces and context).
>
> This is to make sure the viewport of the context is re-initial
'ViewportInitialized' flag in gl_context has to be reset to '0'
when the current context is unbound via a eglMakeCurrent call with
all of 'NULL' resources (surfaces and context).
This is to make sure the viewport of the context is re-initialized
when the same context is bound to new read and draw
