forked from enlightenment/efl
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.
This commit is contained in:
parent
f354463dc1
commit
440238a899
|
@ -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)
|
||||
{
|
||||
|
|
Loading…
Reference in New Issue