On Tue, 19 Apr 2011 10:33:07 +0900 "Sung W. Park" said:
thanks! in svn it is!
> ok, i'm attaching a new patch.
>
> the patch basically checks to see if the current context is evas' gl context
> and if it is, it'll call evas_gl_common_context_flush(). I think this
> is the proper
> way to go.
ok, i'm attaching a new patch.
the patch basically checks to see if the current context is evas' gl context
and if it is, it'll call evas_gl_common_context_flush(). I think this
is the proper
way to go. :-)
cheers,
sung
On Mon, Apr 18, 2011 at 6:39 PM, Sung W. Park wrote:
> well, you're actua
well, you're actually right. I was a little concerned about that aspect but
now that you
point it out, it makes sense with multiple windows.
The real issue is that we have is evas_gl butting in and changing the
currrent context that evas isn't aware of. the proper way to resolve
this would be fo
On Wed, 13 Apr 2011 12:23:22 +0900 "Sung W. Park" said:
that patch seems wrong. if you are changing target window... and you have a
previous window.. it flushes the gl render queue for the previous window target
(or if the flush/use of the window) is flushed. you move the flush to AFTER
setting t
Hi all,
I've been toying around with creating a simple GLView smart object that
allows users do GL rendering simply. Eventually, I would like to see this
as an Elementary widget called GLView. The idea behind this is that
if evas_gl provides the low level stuff, GLView gives the simplified
user-
