hi all;
as you might have noticed, work on Clutter trunk is progressing quite
nicely. obviously, the big question is: towards what? which features
will land in 1.0? will it be called 1.0? when will it be released? what
happens next? when do I get a pony?
well, it was more than one question.
On Tue, 2008-11-11 at 15:26 -0800, David Lock wrote:
Does anyone know the specifics as to why cogl inverts your tex coords
when theyre backward? Is that method of mirroring not supported on
all hardware perhaps?
This is discussed in bug #1057 [1]. The original reason it did this I
think was
Are there any plans to have something similar to GtkClutterViewport but that
can contain multiple actors - like embedding the stage in the viewport and
applying a size limit? The limit of a single actor makes GtkClutterViewport
reasonably useless.
On Thu, 2008-11-13 at 06:47 +1000, Saul Lethbridge wrote:
Are there any plans to have something similar to GtkClutterViewport
but that can contain multiple actors - like embedding the stage in the
viewport and applying a size limit? The limit of a single actor makes
GtkClutterViewport
On Thu, 2008-11-06 at 10:04 +, Matthew Allum wrote:
Hi;
On Wed, 2008-11-05 at 13:03 -0500, Owen Taylor wrote:
I think making it usage explicit and contained like this is really the
only way to go in we do bring back in support for ARB_texture_rectangle
without a lot of
Hi;
On Wed, 2008-11-12 at 17:04 -0500, Owen Taylor wrote:
What about, in my patch, changing COGL_TEXTURE_ALLOW_RECTANGLE
to COGL_TEXTURE_ALLOW_RECTANGLE COGL_TEXTURE_ALLOW_LEGACY_RECTANGLE
and adding a scary warning like:
GL_ARB_texture_rectangle rectangle has numerous limitations,
On Wed, 2008-11-12 at 23:51 +, Matthew Allum wrote:
Hi;
On Wed, 2008-11-12 at 17:04 -0500, Owen Taylor wrote:
What about, in my patch, changing COGL_TEXTURE_ALLOW_RECTANGLE
to COGL_TEXTURE_ALLOW_RECTANGLE COGL_TEXTURE_ALLOW_LEGACY_RECTANGLE
and adding a scary warning like:
Hi,
Is it good to use gboolean as return type for query some bit masked propety?
For example, clutter_actor_get_reactive return CLUTTER_ACTOR_IS_REACTIVE
(actor), it is neither TRUE nor FALSE in glib 's definition. So there is a
potential problem if people compare the return value of these
