On Thu, 2008-09-25 at 00:48 +0100, Robert Bragg wrote:
The nicest approach we've come up with so far seems to be getting
Clutter to internally push the rendering out to a worker thread by
moving the calls to glXSwapBuffer into a new thread. Since writing multi
threaded GL apps is pretty
On Thu, 2008-09-25 at 09:16 +0100, Emmanuele Bassi wrote:
and while GLib data structures and MainLoop are usually thread safe,
GType instantiation is not entirely thread safe (try creating two new
instances of the same class from the same thread).
I don't think the threading issues are so much
On Thu, 2008-09-25 at 10:06 +0100, Emmanuele Bassi wrote:
(I think your clock might be wrong there?)
what I meant was: pushing Clutter towards a heavier threads usage, in
itself is a worthy goal at that, will require some serious rethinking of
how the API should interact with threads.
Ok, so
hi everyone;
Clutter 0.8.2 is now available for download at:
http://www.clutter-project.org/sources/clutter/0.8/
MD5 Checksums:
2e86641254260b355d235ee202918b1c clutter-0.8.2.tar.gz
6fd2c0e63d904523a773736cbb45d176 clutter-0.8.2.tar.bz2
Clutter is an open source software library for
hi all;
after the 0.8.2 release, Clutter core and other submodules branched off
to allow further development to happen on trunk.
clutter - clutter/branches/clutter-0-8
clutter-cairo - clutter/branches/clutter-cairo-0-8
clutter-gst - clutter/branches/clutter-gst-0-8
clutter-gtk
On Thu, 2008-09-25 at 09:16 +0100, Emmanuele Bassi wrote:
threading and python are two very different beasts, with different
interactions at different levels. python is using user-level threads in
its API, as far as I know, and this is already not entirely well
behaving with the concept of
Hi Dilip,
When the requirement is to put content of offscreen to display, why not to
use window surface?
could you write a bit ..
-vinay H
On Wed, Sep 24, 2008 at 1:50 PM, dilip devaraj [EMAIL PROTECTED]wrote:
Hello Clutter Team
I was looking for the offscreen implementation of glx.In
