cedric pushed a commit to branch master. http://git.enlightenment.org/core/efl.git/commit/?id=440238a899166007c859610a0a2825718429797a
commit 440238a899166007c859610a0a2825718429797a Author: Cedric BAIL <[email protected]> Date: Fri Aug 25 10:52:48 2017 -0700 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. --- src/lib/evas/canvas/evas_canvas3d_texture.c | 1 + 1 file changed, 1 insertion(+) 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 eina_hash_foreach(pd->materials, _texture_material_change_notify, obj); } +/* FIXME: This code is problematic as it actually does rendering and rely on the output before we start rendering. */ EOLIAN static void _evas_canvas3d_texture_evas_canvas3d_object_update_notify(Eo *obj, Evas_Canvas3D_Texture_Data *pd) { --
