2008-04-25 09:37:36 -04:00
|
|
|
/*
|
2009-04-27 10:48:12 -04:00
|
|
|
* Cogl
|
2008-04-25 09:37:36 -04:00
|
|
|
*
|
2009-04-27 10:48:12 -04:00
|
|
|
* An object oriented GL/GLES Abstraction/Utility Layer
|
2008-04-25 09:37:36 -04:00
|
|
|
*
|
2009-04-27 10:48:12 -04:00
|
|
|
* Copyright (C) 2007,2008,2009 Intel Corporation.
|
2008-04-25 09:37:36 -04:00
|
|
|
*
|
|
|
|
* This library is free software; you can redistribute it and/or
|
|
|
|
* modify it under the terms of the GNU Lesser General Public
|
|
|
|
* License as published by the Free Software Foundation; either
|
|
|
|
* version 2 of the License, or (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This library is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
|
|
|
|
* Lesser General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU Lesser General Public
|
2010-03-01 07:56:10 -05:00
|
|
|
* License along with this library. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*
|
|
|
|
*
|
2008-04-25 09:37:36 -04:00
|
|
|
*/
|
|
|
|
|
2010-11-04 18:25:52 -04:00
|
|
|
#ifndef __COGL_CONTEXT_PRIVATE_H
|
|
|
|
#define __COGL_CONTEXT_PRIVATE_H
|
2008-04-25 09:37:36 -04:00
|
|
|
|
2009-10-13 18:09:42 -04:00
|
|
|
#include "cogl-internal.h"
|
2010-11-04 20:00:25 -04:00
|
|
|
#include "cogl-context.h"
|
2010-11-05 08:28:33 -04:00
|
|
|
#include "cogl-winsys-private.h"
|
2011-04-15 10:39:14 -04:00
|
|
|
#include "cogl-flags.h"
|
2010-11-05 08:28:33 -04:00
|
|
|
|
|
|
|
#ifdef COGL_HAS_XLIB_SUPPORT
|
|
|
|
#include "cogl-xlib-private.h"
|
|
|
|
#endif
|
2010-09-13 06:30:30 -04:00
|
|
|
|
2010-11-05 08:28:33 -04:00
|
|
|
#include "cogl-display-private.h"
|
2008-04-25 09:37:36 -04:00
|
|
|
#include "cogl-primitives.h"
|
2008-12-04 08:45:09 -05:00
|
|
|
#include "cogl-clip-stack.h"
|
2009-02-24 13:51:25 -05:00
|
|
|
#include "cogl-matrix-stack.h"
|
2010-10-27 13:54:57 -04:00
|
|
|
#include "cogl-pipeline-private.h"
|
2010-01-10 12:28:24 -05:00
|
|
|
#include "cogl-buffer-private.h"
|
2010-05-24 07:40:11 -04:00
|
|
|
#include "cogl-bitmask.h"
|
2010-08-02 11:29:10 -04:00
|
|
|
#include "cogl-atlas.h"
|
2012-03-22 12:32:56 -04:00
|
|
|
#include "cogl-driver.h"
|
2011-07-07 07:48:24 -04:00
|
|
|
#include "cogl-texture-driver.h"
|
2011-06-30 10:55:56 -04:00
|
|
|
#include "cogl-pipeline-cache.h"
|
2012-02-18 09:58:39 -05:00
|
|
|
#include "cogl-texture-2d.h"
|
|
|
|
#include "cogl-texture-3d.h"
|
|
|
|
#include "cogl-texture-rectangle.h"
|
2012-04-04 17:20:04 -04:00
|
|
|
#include "cogl-sampler-cache-private.h"
|
2012-03-27 09:43:04 -04:00
|
|
|
#include "cogl-gpu-info-private.h"
|
2012-03-23 14:05:46 -04:00
|
|
|
#include "cogl-gl-header.h"
|
2008-05-27 13:42:50 -04:00
|
|
|
|
2008-04-25 09:37:36 -04:00
|
|
|
typedef struct
|
|
|
|
{
|
2008-11-18 11:24:09 -05:00
|
|
|
GLfloat v[3];
|
|
|
|
GLfloat t[2];
|
|
|
|
GLubyte c[4];
|
2008-04-25 09:37:36 -04:00
|
|
|
} CoglTextureGLVertex;
|
|
|
|
|
2010-11-04 20:00:25 -04:00
|
|
|
struct _CoglContext
|
2008-04-25 09:37:36 -04:00
|
|
|
{
|
2010-11-04 20:00:25 -04:00
|
|
|
CoglObject _parent;
|
|
|
|
|
2010-11-05 08:28:33 -04:00
|
|
|
CoglDisplay *display;
|
|
|
|
|
2011-07-07 15:44:56 -04:00
|
|
|
CoglDriver driver;
|
|
|
|
|
2012-03-27 09:43:04 -04:00
|
|
|
/* Information about the GPU and driver which we can use to
|
|
|
|
determine certain workarounds */
|
|
|
|
CoglGpuInfo gpu;
|
|
|
|
|
2012-03-22 12:32:56 -04:00
|
|
|
/* vtables for the driver functions */
|
|
|
|
const CoglDriverVtable *driver_vtable;
|
2011-07-07 07:48:24 -04:00
|
|
|
const CoglTextureDriver *texture_driver;
|
|
|
|
|
2008-04-25 09:37:36 -04:00
|
|
|
/* Features cache */
|
2011-10-31 10:19:10 -04:00
|
|
|
unsigned long features[COGL_FLAGS_N_LONGS_FOR_SIZE (_COGL_N_FEATURE_IDS)];
|
2011-10-12 17:31:12 -04:00
|
|
|
CoglFeatureFlags feature_flags; /* legacy/deprecated feature flags */
|
2011-05-24 17:34:10 -04:00
|
|
|
CoglPrivateFeatureFlags private_feature_flags;
|
2009-01-26 06:07:35 -05:00
|
|
|
|
2012-02-18 09:58:39 -05:00
|
|
|
CoglPipeline *default_pipeline;
|
|
|
|
CoglPipelineLayer *default_layer_0;
|
|
|
|
CoglPipelineLayer *default_layer_n;
|
|
|
|
CoglPipelineLayer *dummy_layer_dependant;
|
2009-11-11 07:50:48 -05:00
|
|
|
|
2011-11-24 13:09:53 -05:00
|
|
|
GHashTable *attribute_name_states_hash;
|
|
|
|
GArray *attribute_name_index_map;
|
|
|
|
int n_attribute_names;
|
|
|
|
|
|
|
|
CoglBitmask enabled_builtin_attributes;
|
|
|
|
CoglBitmask enabled_texcoord_attributes;
|
|
|
|
CoglBitmask enabled_custom_attributes;
|
|
|
|
|
|
|
|
/* These are temporary bitmasks that are used when disabling
|
|
|
|
* builtin,texcoord and custom attribute arrays. They are here just
|
|
|
|
* to avoid allocating new ones each time */
|
|
|
|
CoglBitmask enable_builtin_attributes_tmp;
|
|
|
|
CoglBitmask enable_texcoord_attributes_tmp;
|
|
|
|
CoglBitmask enable_custom_attributes_tmp;
|
|
|
|
CoglBitmask changed_bits_tmp;
|
2009-01-26 06:07:35 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool legacy_backface_culling_enabled;
|
2009-07-27 20:34:33 -04:00
|
|
|
|
2009-10-22 11:13:01 -04:00
|
|
|
/* A few handy matrix constants */
|
|
|
|
CoglMatrix identity_matrix;
|
|
|
|
CoglMatrix y_flip_matrix;
|
|
|
|
|
2011-11-29 09:21:07 -05:00
|
|
|
/* Value that was last used when calling glMatrixMode to avoid
|
|
|
|
calling it multiple times */
|
2009-10-14 05:53:48 -04:00
|
|
|
CoglMatrixMode flushed_matrix_mode;
|
2010-04-26 05:01:43 -04:00
|
|
|
|
Re-design the matrix stack using a graph of ops
This re-designs the matrix stack so we now keep track of each separate
operation such as rotating, scaling, translating and multiplying as
immutable, ref-counted nodes in a graph.
Being a "graph" here means that different transformations composed of
a sequence of linked operation nodes may share nodes.
The first node in a matrix-stack is always a LOAD_IDENTITY operation.
As an example consider if an application where to draw three rectangles
A, B and C something like this:
cogl_framebuffer_scale (fb, 2, 2, 2);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_translate (fb, 10, 0, 0);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_rotate (fb, 45, 0, 0, 1);
cogl_framebuffer_draw_rectangle (...); /* A */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_draw_rectangle (...); /* B */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_set_modelview_matrix (fb, &mv);
cogl_framebuffer_draw_rectangle (...); /* C */
cogl_framebuffer_pop_matrix(fb);
That would result in a graph of nodes like this:
LOAD_IDENTITY
|
SCALE
/ \
SAVE LOAD
| |
TRANSLATE RECTANGLE(C)
| \
SAVE RECTANGLE(B)
|
ROTATE
|
RECTANGLE(A)
Each push adds a SAVE operation which serves as a marker to rewind too
when a corresponding pop is issued and also each SAVE node may also
store a cached matrix representing the composition of all its ancestor
nodes. This means if we repeatedly need to resolve a real CoglMatrix
for a given node then we don't need to repeat the composition.
Some advantages of this design are:
- A single pointer to any node in the graph can now represent a
complete, immutable transformation that can be logged for example
into a journal. Previously we were storing a full CoglMatrix in
each journal entry which is 16 floats for the matrix itself as well
as space for flags and another 16 floats for possibly storing a
cache of the inverse. This means that we significantly reduce
the size of the journal when drawing lots of primitives and we also
avoid copying over 128 bytes per entry.
- It becomes much cheaper to check for equality. In cases where some
(unlikely) false negatives are allowed simply comparing the pointers
of two matrix stack graph entries is enough. Previously we would use
memcmp() to compare matrices.
- It becomes easier to do comparisons of transformations. By looking
for the common ancestry between nodes we can determine the operations
that differentiate the transforms and use those to gain a high level
understanding of the differences. For example we use this in the
journal to be able to efficiently determine when two rectangle
transforms only differ by some translation so that we can perform
software clipping.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit f75aee93f6b293ca7a7babbd8fcc326ee6bf7aef)
2012-02-20 10:59:48 -05:00
|
|
|
/* The matrix stack entries that should be flushed during the next
|
|
|
|
* pipeline state flush */
|
|
|
|
CoglMatrixEntry *current_projection_entry;
|
|
|
|
CoglMatrixEntry *current_modelview_entry;
|
2011-11-29 09:21:07 -05:00
|
|
|
|
Re-design the matrix stack using a graph of ops
This re-designs the matrix stack so we now keep track of each separate
operation such as rotating, scaling, translating and multiplying as
immutable, ref-counted nodes in a graph.
Being a "graph" here means that different transformations composed of
a sequence of linked operation nodes may share nodes.
The first node in a matrix-stack is always a LOAD_IDENTITY operation.
As an example consider if an application where to draw three rectangles
A, B and C something like this:
cogl_framebuffer_scale (fb, 2, 2, 2);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_translate (fb, 10, 0, 0);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_rotate (fb, 45, 0, 0, 1);
cogl_framebuffer_draw_rectangle (...); /* A */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_draw_rectangle (...); /* B */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_set_modelview_matrix (fb, &mv);
cogl_framebuffer_draw_rectangle (...); /* C */
cogl_framebuffer_pop_matrix(fb);
That would result in a graph of nodes like this:
LOAD_IDENTITY
|
SCALE
/ \
SAVE LOAD
| |
TRANSLATE RECTANGLE(C)
| \
SAVE RECTANGLE(B)
|
ROTATE
|
RECTANGLE(A)
Each push adds a SAVE operation which serves as a marker to rewind too
when a corresponding pop is issued and also each SAVE node may also
store a cached matrix representing the composition of all its ancestor
nodes. This means if we repeatedly need to resolve a real CoglMatrix
for a given node then we don't need to repeat the composition.
Some advantages of this design are:
- A single pointer to any node in the graph can now represent a
complete, immutable transformation that can be logged for example
into a journal. Previously we were storing a full CoglMatrix in
each journal entry which is 16 floats for the matrix itself as well
as space for flags and another 16 floats for possibly storing a
cache of the inverse. This means that we significantly reduce
the size of the journal when drawing lots of primitives and we also
avoid copying over 128 bytes per entry.
- It becomes much cheaper to check for equality. In cases where some
(unlikely) false negatives are allowed simply comparing the pointers
of two matrix stack graph entries is enough. Previously we would use
memcmp() to compare matrices.
- It becomes easier to do comparisons of transformations. By looking
for the common ancestry between nodes we can determine the operations
that differentiate the transforms and use those to gain a high level
understanding of the differences. For example we use this in the
journal to be able to efficiently determine when two rectangle
transforms only differ by some translation so that we can perform
software clipping.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit f75aee93f6b293ca7a7babbd8fcc326ee6bf7aef)
2012-02-20 10:59:48 -05:00
|
|
|
CoglMatrixEntry identity_entry;
|
|
|
|
|
|
|
|
/* A cache of the last (immutable) matrix stack entries that were
|
|
|
|
* flushed to the GL matrix builtins */
|
|
|
|
CoglMatrixEntryCache builtin_flushed_projection;
|
|
|
|
CoglMatrixEntryCache builtin_flushed_modelview;
|
2010-12-06 07:31:51 -05:00
|
|
|
|
2010-04-26 05:01:43 -04:00
|
|
|
GArray *texture_units;
|
|
|
|
int active_texture_unit;
|
2009-02-24 13:51:25 -05:00
|
|
|
|
2010-10-27 13:54:57 -04:00
|
|
|
CoglPipelineFogState legacy_fog_state;
|
2010-07-06 15:18:26 -04:00
|
|
|
|
2010-11-01 16:27:32 -04:00
|
|
|
/* Pipelines */
|
|
|
|
CoglPipeline *opaque_color_pipeline; /* used for set_source_color */
|
|
|
|
CoglPipeline *blended_color_pipeline; /* used for set_source_color */
|
2010-10-27 13:54:57 -04:00
|
|
|
CoglPipeline *texture_pipeline; /* used for set_source_texture */
|
2010-12-02 13:05:22 -05:00
|
|
|
GString *codegen_header_buffer;
|
|
|
|
GString *codegen_source_buffer;
|
2010-10-25 08:25:21 -04:00
|
|
|
GList *source_stack;
|
2010-04-26 05:01:43 -04:00
|
|
|
|
|
|
|
int legacy_state_set;
|
2009-01-26 06:07:35 -05:00
|
|
|
|
2011-06-30 10:55:56 -04:00
|
|
|
CoglPipelineCache *pipeline_cache;
|
2010-12-03 07:01:18 -05:00
|
|
|
|
2009-01-26 06:07:35 -05:00
|
|
|
/* Textures */
|
2012-02-18 09:58:39 -05:00
|
|
|
CoglTexture2D *default_gl_texture_2d_tex;
|
|
|
|
CoglTexture3D *default_gl_texture_3d_tex;
|
|
|
|
CoglTextureRectangle *default_gl_texture_rect_tex;
|
2009-01-26 06:07:35 -05:00
|
|
|
|
2011-01-06 08:25:45 -05:00
|
|
|
/* Central list of all framebuffers so all journals can be flushed
|
|
|
|
* at any time. */
|
|
|
|
GList *framebuffers;
|
|
|
|
|
|
|
|
/* Global journal buffers */
|
2010-10-26 14:22:57 -04:00
|
|
|
GArray *journal_flush_attributes_array;
|
2010-11-09 14:18:37 -05:00
|
|
|
GArray *journal_clip_bounds;
|
2009-01-26 06:07:35 -05:00
|
|
|
|
2010-10-18 12:17:22 -04:00
|
|
|
GArray *polygon_vertices;
|
|
|
|
|
2009-01-26 06:07:35 -05:00
|
|
|
/* Some simple caching, to minimize state changes... */
|
2010-10-27 13:54:57 -04:00
|
|
|
CoglPipeline *current_pipeline;
|
|
|
|
unsigned long current_pipeline_changes_since_flush;
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool current_pipeline_skip_gl_color;
|
2010-10-27 13:54:57 -04:00
|
|
|
unsigned long current_pipeline_age;
|
2010-04-08 07:21:04 -04:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool gl_blend_enable_cache;
|
2010-04-08 07:21:04 -04:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool depth_test_enabled_cache;
|
2010-05-26 06:33:32 -04:00
|
|
|
CoglDepthTestFunction depth_test_function_cache;
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool depth_writing_enabled_cache;
|
2010-05-26 06:33:32 -04:00
|
|
|
float depth_range_near_cache;
|
|
|
|
float depth_range_far_cache;
|
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool legacy_depth_test_enabled;
|
2010-05-26 06:33:32 -04:00
|
|
|
|
2010-07-05 18:24:34 -04:00
|
|
|
CoglBuffer *current_buffer[COGL_BUFFER_BIND_TARGET_COUNT];
|
2010-01-10 12:28:24 -05:00
|
|
|
|
2009-11-26 14:06:35 -05:00
|
|
|
/* Framebuffers */
|
|
|
|
GSList *framebuffer_stack;
|
2012-04-16 09:14:10 -04:00
|
|
|
CoglFramebuffer *window_buffer;
|
2011-11-21 10:53:40 -05:00
|
|
|
unsigned long current_draw_buffer_state_flushed;
|
|
|
|
unsigned long current_draw_buffer_changes;
|
|
|
|
CoglFramebuffer *current_draw_buffer;
|
|
|
|
CoglFramebuffer *current_read_buffer;
|
2009-01-26 06:07:35 -05:00
|
|
|
|
|
|
|
/* Primitives */
|
2010-11-03 20:27:47 -04:00
|
|
|
CoglPath *current_path;
|
2010-10-27 13:54:57 -04:00
|
|
|
CoglPipeline *stencil_pipeline;
|
2008-12-04 08:45:09 -05:00
|
|
|
|
2009-05-28 08:47:18 -04:00
|
|
|
/* Pre-generated VBOs containing indices to generate GL_TRIANGLES
|
|
|
|
out of a vertex array of quads */
|
2012-04-16 09:14:10 -04:00
|
|
|
CoglIndices *quad_buffer_indices_byte;
|
2010-10-12 07:48:58 -04:00
|
|
|
unsigned int quad_buffer_indices_len;
|
2012-04-16 09:14:10 -04:00
|
|
|
CoglIndices *quad_buffer_indices;
|
2010-10-12 07:48:58 -04:00
|
|
|
|
|
|
|
CoglIndices *rectangle_byte_indices;
|
|
|
|
CoglIndices *rectangle_short_indices;
|
|
|
|
int rectangle_short_indices_len;
|
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool in_begin_gl_block;
|
2009-07-18 11:59:54 -04:00
|
|
|
|
2010-10-27 13:54:57 -04:00
|
|
|
CoglPipeline *texture_download_pipeline;
|
2011-01-20 12:45:47 -05:00
|
|
|
CoglPipeline *blit_texture_pipeline;
|
2009-08-30 06:36:11 -04:00
|
|
|
|
2010-11-27 08:15:02 -05:00
|
|
|
GSList *atlases;
|
2011-03-30 07:53:50 -04:00
|
|
|
GHookList atlas_reorganize_callbacks;
|
2009-12-04 08:06:32 -05:00
|
|
|
|
2010-01-22 13:14:57 -05:00
|
|
|
/* This debugging variable is used to pick a colour for visually
|
|
|
|
displaying the quad batches. It needs to be global so that it can
|
|
|
|
be reset by cogl_clear. It needs to be reset to increase the
|
|
|
|
chances of getting the same colour during an animation */
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
uint8_t journal_rectangles_color;
|
2010-01-22 13:14:57 -05:00
|
|
|
|
2010-04-26 05:01:43 -04:00
|
|
|
/* Cached values for GL_MAX_TEXTURE_[IMAGE_]UNITS to avoid calling
|
2010-02-12 09:26:33 -05:00
|
|
|
glGetInteger too often */
|
|
|
|
GLint max_texture_units;
|
2010-04-26 05:01:43 -04:00
|
|
|
GLint max_texture_image_units;
|
|
|
|
GLint max_activateable_texture_units;
|
|
|
|
|
2010-04-08 07:21:04 -04:00
|
|
|
/* Fragment processing programs */
|
|
|
|
CoglHandle current_program;
|
|
|
|
|
2010-12-02 15:48:45 -05:00
|
|
|
CoglPipelineProgramType current_fragment_program_type;
|
|
|
|
CoglPipelineProgramType current_vertex_program_type;
|
2010-04-08 07:21:04 -04:00
|
|
|
GLuint current_gl_program;
|
2010-02-12 09:26:33 -05:00
|
|
|
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool current_gl_dither_enabled;
|
2011-07-10 21:27:54 -04:00
|
|
|
CoglColorMask current_gl_color_mask;
|
2011-07-13 11:33:25 -04:00
|
|
|
|
2010-06-11 08:50:36 -04:00
|
|
|
/* List of types that will be considered a subclass of CoglTexture in
|
|
|
|
cogl_is_texture */
|
|
|
|
GSList *texture_types;
|
|
|
|
|
2010-07-03 18:56:44 -04:00
|
|
|
/* List of types that will be considered a subclass of CoglBuffer in
|
|
|
|
cogl_is_buffer */
|
|
|
|
GSList *buffer_types;
|
|
|
|
|
2010-11-02 10:28:12 -04:00
|
|
|
/* Clipping */
|
|
|
|
/* TRUE if we have a valid clipping stack flushed. In that case
|
|
|
|
current_clip_stack will describe what the current state is. If
|
|
|
|
this is FALSE then the current clip stack is completely unknown
|
|
|
|
so it will need to be reflushed. In that case current_clip_stack
|
|
|
|
doesn't need to be a valid pointer. We can't just use NULL in
|
|
|
|
current_clip_stack to mark a dirty state because NULL is a valid
|
|
|
|
stack (meaning no clipping) */
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool current_clip_stack_valid;
|
2010-11-02 10:28:12 -04:00
|
|
|
/* The clip state that was flushed. This isn't intended to be used
|
|
|
|
as a stack to push and pop new entries. Instead the current stack
|
|
|
|
that the user wants is part of the framebuffer state. This is
|
|
|
|
just used to record the flush state so we can avoid flushing the
|
|
|
|
same state multiple times. When the clip state is flushed this
|
|
|
|
will hold a reference */
|
|
|
|
CoglClipStack *current_clip_stack;
|
|
|
|
/* Whether the stencil buffer was used as part of the current clip
|
|
|
|
state. If TRUE then any further use of the stencil buffer (such
|
|
|
|
as for drawing paths) would need to be merged with the existing
|
|
|
|
stencil buffer */
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool current_clip_stack_uses_stencil;
|
2010-11-02 10:28:12 -04:00
|
|
|
|
2011-01-13 10:35:30 -05:00
|
|
|
/* This is used as a temporary buffer to fill a CoglBuffer when
|
|
|
|
cogl_buffer_map fails and we only want to map to fill it with new
|
|
|
|
data */
|
|
|
|
GByteArray *buffer_map_fallback_array;
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool buffer_map_fallback_in_use;
|
2011-01-13 10:35:30 -05:00
|
|
|
|
2010-11-05 08:28:33 -04:00
|
|
|
CoglWinsysRectangleState rectangle_state;
|
|
|
|
|
2012-04-04 17:20:04 -04:00
|
|
|
CoglSamplerCache *sampler_cache;
|
|
|
|
|
2010-11-05 08:28:33 -04:00
|
|
|
/* FIXME: remove these when we remove the last xlib based clutter
|
|
|
|
* backend. they should be tracked as part of the renderer but e.g.
|
|
|
|
* the eglx backend doesn't yet have a corresponding Cogl winsys
|
|
|
|
* and so we wont have a renderer in that case. */
|
|
|
|
#ifdef COGL_HAS_XLIB_SUPPORT
|
|
|
|
int damage_base;
|
|
|
|
/* List of callback functions that will be given every Xlib event */
|
|
|
|
GSList *event_filters;
|
|
|
|
/* Current top of the XError trap state stack. The actual memory for
|
|
|
|
these is expected to be allocated on the stack by the caller */
|
|
|
|
CoglXlibTrapState *trap_state;
|
|
|
|
#endif
|
|
|
|
|
2011-10-31 10:19:10 -04:00
|
|
|
unsigned long winsys_features
|
|
|
|
[COGL_FLAGS_N_LONGS_FOR_SIZE (COGL_WINSYS_FEATURE_N_FEATURES)];
|
2010-11-05 08:28:33 -04:00
|
|
|
void *winsys;
|
2011-07-06 13:59:20 -04:00
|
|
|
|
2011-11-04 14:26:17 -04:00
|
|
|
/* Array of names of uniforms. These are used like quarks to give a
|
cogl-pipeline: Add support for setting uniform values
This adds the following new public experimental functions to set
uniform values on a CoglPipeline:
void
cogl_pipeline_set_uniform_1f (CoglPipeline *pipeline,
int uniform_location,
float value);
void
cogl_pipeline_set_uniform_1i (CoglPipeline *pipeline,
int uniform_location,
int value);
void
cogl_pipeline_set_uniform_float (CoglPipeline *pipeline,
int uniform_location,
int n_components,
int count,
const float *value);
void
cogl_pipeline_set_uniform_int (CoglPipeline *pipeline,
int uniform_location,
int n_components,
int count,
const int *value);
void
cogl_pipeline_set_uniform_matrix (CoglPipeline *pipeline,
int uniform_location,
int dimensions,
int count,
gboolean transpose,
const float *value);
These are similar to the old functions used to set uniforms on a
CoglProgram. To get a value to pass in as the uniform_location there
is also:
int
cogl_pipeline_get_uniform_location (CoglPipeline *pipeline,
const char *uniform_name);
Conceptually the uniform locations are tied to the pipeline so that
whenever setting a value for a new pipeline the application is
expected to call this function. However in practice the uniform
locations are global to the CoglContext. The names are stored in a
linked list where the position in the list is the uniform location.
The global indices are used so that each pipeline can store a mask of
which uniforms it overrides. That way it is quicker to detect which
uniforms are different from the last pipeline that used the same
CoglProgramState so it can avoid flushing uniforms that haven't
changed. Currently the values are not actually compared which means
that it will only avoid flushing a uniform if there is a common
ancestor that sets the value (or if the same pipeline is being flushed
again - in which case the pipeline and its common ancestor are the
same thing).
The uniform values are stored in the big state of the pipeline as a
sparse linked list. A bitmask stores which values have been overridden
and only overridden values are stored in the linked list.
Reviewed-by: Robert Bragg <robert@linux.intel.com>
2011-11-03 13:20:43 -04:00
|
|
|
unique number to each uniform name except that we ensure that
|
|
|
|
they increase sequentially so that we can use the id as an index
|
|
|
|
into a bitfield representing the uniforms that a pipeline
|
2011-11-04 14:26:17 -04:00
|
|
|
overrides from its parent. */
|
|
|
|
GPtrArray *uniform_names;
|
|
|
|
/* A hash table to quickly get an index given an existing name. The
|
|
|
|
name strings are owned by the uniform_names array. The values are
|
|
|
|
the uniform location cast to a pointer. */
|
|
|
|
GHashTable *uniform_name_hash;
|
cogl-pipeline: Add support for setting uniform values
This adds the following new public experimental functions to set
uniform values on a CoglPipeline:
void
cogl_pipeline_set_uniform_1f (CoglPipeline *pipeline,
int uniform_location,
float value);
void
cogl_pipeline_set_uniform_1i (CoglPipeline *pipeline,
int uniform_location,
int value);
void
cogl_pipeline_set_uniform_float (CoglPipeline *pipeline,
int uniform_location,
int n_components,
int count,
const float *value);
void
cogl_pipeline_set_uniform_int (CoglPipeline *pipeline,
int uniform_location,
int n_components,
int count,
const int *value);
void
cogl_pipeline_set_uniform_matrix (CoglPipeline *pipeline,
int uniform_location,
int dimensions,
int count,
gboolean transpose,
const float *value);
These are similar to the old functions used to set uniforms on a
CoglProgram. To get a value to pass in as the uniform_location there
is also:
int
cogl_pipeline_get_uniform_location (CoglPipeline *pipeline,
const char *uniform_name);
Conceptually the uniform locations are tied to the pipeline so that
whenever setting a value for a new pipeline the application is
expected to call this function. However in practice the uniform
locations are global to the CoglContext. The names are stored in a
linked list where the position in the list is the uniform location.
The global indices are used so that each pipeline can store a mask of
which uniforms it overrides. That way it is quicker to detect which
uniforms are different from the last pipeline that used the same
CoglProgramState so it can avoid flushing uniforms that haven't
changed. Currently the values are not actually compared which means
that it will only avoid flushing a uniform if there is a common
ancestor that sets the value (or if the same pipeline is being flushed
again - in which case the pipeline and its common ancestor are the
same thing).
The uniform values are stored in the big state of the pipeline as a
sparse linked list. A bitmask stores which values have been overridden
and only overridden values are stored in the linked list.
Reviewed-by: Robert Bragg <robert@linux.intel.com>
2011-11-03 13:20:43 -04:00
|
|
|
int n_uniform_names;
|
|
|
|
|
2011-07-06 13:59:20 -04:00
|
|
|
/* This defines a list of function pointers that Cogl uses from
|
|
|
|
either GL or GLES. All functions are accessed indirectly through
|
|
|
|
these pointers rather than linking to them directly */
|
|
|
|
#ifndef APIENTRY
|
|
|
|
#define APIENTRY
|
|
|
|
#endif
|
|
|
|
|
|
|
|
#define COGL_EXT_BEGIN(name, \
|
|
|
|
min_gl_major, min_gl_minor, \
|
|
|
|
gles_availability, \
|
|
|
|
extension_suffixes, extension_names)
|
|
|
|
#define COGL_EXT_FUNCTION(ret, name, args) \
|
|
|
|
ret (APIENTRY * name) args;
|
|
|
|
#define COGL_EXT_END()
|
|
|
|
|
2012-01-01 16:45:07 -05:00
|
|
|
#include "gl-prototypes/cogl-all-functions.h"
|
2011-07-06 13:59:20 -04:00
|
|
|
|
|
|
|
#undef COGL_EXT_BEGIN
|
|
|
|
#undef COGL_EXT_FUNCTION
|
|
|
|
#undef COGL_EXT_END
|
2010-11-04 20:00:25 -04:00
|
|
|
};
|
2008-04-25 09:37:36 -04:00
|
|
|
|
|
|
|
CoglContext *
|
|
|
|
_cogl_context_get_default ();
|
|
|
|
|
2011-02-25 06:29:08 -05:00
|
|
|
const CoglWinsysVtable *
|
|
|
|
_cogl_context_get_winsys (CoglContext *context);
|
|
|
|
|
2011-07-07 15:44:56 -04:00
|
|
|
/* Query the GL extensions and lookup the corresponding function
|
|
|
|
* pointers. Theoretically the list of extensions can change for
|
|
|
|
* different GL contexts so it is the winsys backend's responsiblity
|
2011-07-13 13:29:56 -04:00
|
|
|
* to know when to re-query the GL extensions. The backend should also
|
|
|
|
* check whether the GL context is supported by Cogl. If not it should
|
|
|
|
* return FALSE and set @error */
|
Switch use of primitive glib types to c99 equivalents
The coding style has for a long time said to avoid using redundant glib
data types such as gint or gchar etc because we feel that they make the
code look unnecessarily foreign to developers coming from outside of the
Gnome developer community.
Note: When we tried to find the historical rationale for the types we
just found that they were apparently only added for consistent syntax
highlighting which didn't seem that compelling.
Up until now we have been continuing to use some of the platform
specific type such as gint{8,16,32,64} and gsize but this patch switches
us over to using the standard c99 equivalents instead so we can further
ensure that our code looks familiar to the widest range of C developers
who might potentially contribute to Cogl.
So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this
switches all Cogl code to instead use the int{8,16,32,64}_t and
uint{8,16,32,64}_t c99 types instead.
Instead of gsize we now use size_t
For now we are not going to use the c99 _Bool type and instead we have
introduced a new CoglBool type to use instead of gboolean.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
|
|
|
CoglBool
|
2011-07-13 13:29:56 -04:00
|
|
|
_cogl_context_update_features (CoglContext *context,
|
|
|
|
GError **error);
|
2011-07-07 15:44:56 -04:00
|
|
|
|
2008-04-25 09:37:36 -04:00
|
|
|
/* Obtains the context and returns retval if NULL */
|
|
|
|
#define _COGL_GET_CONTEXT(ctxvar, retval) \
|
|
|
|
CoglContext *ctxvar = _cogl_context_get_default (); \
|
|
|
|
if (ctxvar == NULL) return retval;
|
|
|
|
|
2009-01-26 06:07:35 -05:00
|
|
|
#define NO_RETVAL
|
2008-04-25 09:37:36 -04:00
|
|
|
|
2011-11-29 09:21:07 -05:00
|
|
|
void
|
Re-design the matrix stack using a graph of ops
This re-designs the matrix stack so we now keep track of each separate
operation such as rotating, scaling, translating and multiplying as
immutable, ref-counted nodes in a graph.
Being a "graph" here means that different transformations composed of
a sequence of linked operation nodes may share nodes.
The first node in a matrix-stack is always a LOAD_IDENTITY operation.
As an example consider if an application where to draw three rectangles
A, B and C something like this:
cogl_framebuffer_scale (fb, 2, 2, 2);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_translate (fb, 10, 0, 0);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_rotate (fb, 45, 0, 0, 1);
cogl_framebuffer_draw_rectangle (...); /* A */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_draw_rectangle (...); /* B */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_set_modelview_matrix (fb, &mv);
cogl_framebuffer_draw_rectangle (...); /* C */
cogl_framebuffer_pop_matrix(fb);
That would result in a graph of nodes like this:
LOAD_IDENTITY
|
SCALE
/ \
SAVE LOAD
| |
TRANSLATE RECTANGLE(C)
| \
SAVE RECTANGLE(B)
|
ROTATE
|
RECTANGLE(A)
Each push adds a SAVE operation which serves as a marker to rewind too
when a corresponding pop is issued and also each SAVE node may also
store a cached matrix representing the composition of all its ancestor
nodes. This means if we repeatedly need to resolve a real CoglMatrix
for a given node then we don't need to repeat the composition.
Some advantages of this design are:
- A single pointer to any node in the graph can now represent a
complete, immutable transformation that can be logged for example
into a journal. Previously we were storing a full CoglMatrix in
each journal entry which is 16 floats for the matrix itself as well
as space for flags and another 16 floats for possibly storing a
cache of the inverse. This means that we significantly reduce
the size of the journal when drawing lots of primitives and we also
avoid copying over 128 bytes per entry.
- It becomes much cheaper to check for equality. In cases where some
(unlikely) false negatives are allowed simply comparing the pointers
of two matrix stack graph entries is enough. Previously we would use
memcmp() to compare matrices.
- It becomes easier to do comparisons of transformations. By looking
for the common ancestry between nodes we can determine the operations
that differentiate the transforms and use those to gain a high level
understanding of the differences. For example we use this in the
journal to be able to efficiently determine when two rectangle
transforms only differ by some translation so that we can perform
software clipping.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit f75aee93f6b293ca7a7babbd8fcc326ee6bf7aef)
2012-02-20 10:59:48 -05:00
|
|
|
_cogl_context_set_current_projection_entry (CoglContext *context,
|
|
|
|
CoglMatrixEntry *entry);
|
2011-11-29 09:21:07 -05:00
|
|
|
|
|
|
|
void
|
Re-design the matrix stack using a graph of ops
This re-designs the matrix stack so we now keep track of each separate
operation such as rotating, scaling, translating and multiplying as
immutable, ref-counted nodes in a graph.
Being a "graph" here means that different transformations composed of
a sequence of linked operation nodes may share nodes.
The first node in a matrix-stack is always a LOAD_IDENTITY operation.
As an example consider if an application where to draw three rectangles
A, B and C something like this:
cogl_framebuffer_scale (fb, 2, 2, 2);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_translate (fb, 10, 0, 0);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_rotate (fb, 45, 0, 0, 1);
cogl_framebuffer_draw_rectangle (...); /* A */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_draw_rectangle (...); /* B */
cogl_framebuffer_pop_matrix(fb);
cogl_framebuffer_push_matrix(fb);
cogl_framebuffer_set_modelview_matrix (fb, &mv);
cogl_framebuffer_draw_rectangle (...); /* C */
cogl_framebuffer_pop_matrix(fb);
That would result in a graph of nodes like this:
LOAD_IDENTITY
|
SCALE
/ \
SAVE LOAD
| |
TRANSLATE RECTANGLE(C)
| \
SAVE RECTANGLE(B)
|
ROTATE
|
RECTANGLE(A)
Each push adds a SAVE operation which serves as a marker to rewind too
when a corresponding pop is issued and also each SAVE node may also
store a cached matrix representing the composition of all its ancestor
nodes. This means if we repeatedly need to resolve a real CoglMatrix
for a given node then we don't need to repeat the composition.
Some advantages of this design are:
- A single pointer to any node in the graph can now represent a
complete, immutable transformation that can be logged for example
into a journal. Previously we were storing a full CoglMatrix in
each journal entry which is 16 floats for the matrix itself as well
as space for flags and another 16 floats for possibly storing a
cache of the inverse. This means that we significantly reduce
the size of the journal when drawing lots of primitives and we also
avoid copying over 128 bytes per entry.
- It becomes much cheaper to check for equality. In cases where some
(unlikely) false negatives are allowed simply comparing the pointers
of two matrix stack graph entries is enough. Previously we would use
memcmp() to compare matrices.
- It becomes easier to do comparisons of transformations. By looking
for the common ancestry between nodes we can determine the operations
that differentiate the transforms and use those to gain a high level
understanding of the differences. For example we use this in the
journal to be able to efficiently determine when two rectangle
transforms only differ by some translation so that we can perform
software clipping.
Reviewed-by: Neil Roberts <neil@linux.intel.com>
(cherry picked from commit f75aee93f6b293ca7a7babbd8fcc326ee6bf7aef)
2012-02-20 10:59:48 -05:00
|
|
|
_cogl_context_set_current_modelview_entry (CoglContext *context,
|
|
|
|
CoglMatrixEntry *entry);
|
2011-11-29 09:21:07 -05:00
|
|
|
|
2010-11-04 18:25:52 -04:00
|
|
|
#endif /* __COGL_CONTEXT_PRIVATE_H */
|