summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCedric BAIL <cedric@osg.samsung.com>2017-08-25 10:52:48 -0700
committerCedric BAIL <cedric@osg.samsung.com>2017-08-25 10:52:48 -0700
commit440238a899166007c859610a0a2825718429797a (patch)
treea34ff56484ce001a7f96554f5cecdff6da474084
parentf354463dc1524da7e2475f3aab893959fcdc4e54 (diff)
evas: Evas_Canvas3D rendering logic need a complete overhaul.
For now, do not use Evas_Canvas3D in multi output context, it won't work. The update code for Evas_Canvas3D_Node might trigger rendering logic, which is opposite to what the scene graph logic should do. It require to much reshuffle around to handle that case at the moment. So I am just adding a warning.
-rw-r--r--src/lib/evas/canvas/evas_canvas3d_texture.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/src/lib/evas/canvas/evas_canvas3d_texture.c b/src/lib/evas/canvas/evas_canvas3d_texture.c
index 2876364591..6471ddafbd 100644
--- a/src/lib/evas/canvas/evas_canvas3d_texture.c
+++ b/src/lib/evas/canvas/evas_canvas3d_texture.c
@@ -220,6 +220,7 @@ _evas_canvas3d_texture_evas_canvas3d_object_change_notify(Eo *obj, Evas_Canvas3D
220 eina_hash_foreach(pd->materials, _texture_material_change_notify, obj); 220 eina_hash_foreach(pd->materials, _texture_material_change_notify, obj);
221} 221}
222 222
223/* FIXME: This code is problematic as it actually does rendering and rely on the output before we start rendering. */
223EOLIAN static void 224EOLIAN static void
224_evas_canvas3d_texture_evas_canvas3d_object_update_notify(Eo *obj, Evas_Canvas3D_Texture_Data *pd) 225_evas_canvas3d_texture_evas_canvas3d_object_update_notify(Eo *obj, Evas_Canvas3D_Texture_Data *pd)
225{ 226{