ecore_evas: fix evas_changed call
Don't or together all previously considered evases. Thanks Cedric for the catch.
This commit is contained in:
parent
8215d9832c
commit
2480b4bb22
|
@ -174,15 +174,20 @@ _ecore_evas_idle_enter(void *data EINA_UNUSED)
|
|||
|
||||
if (!ee->manual_render)
|
||||
{
|
||||
Eina_Bool change = EINA_FALSE;
|
||||
|
||||
if (ee->engine.func->fn_render)
|
||||
rend |= ee->engine.func->fn_render(ee);
|
||||
{
|
||||
change = ee->engine.func->fn_render(ee);
|
||||
rend |= change;
|
||||
}
|
||||
/*
|
||||
* Some engines that generate their own ticks based on hardware
|
||||
* events need to know that render has been considered, and
|
||||
* whether it will actually generate a new image or not
|
||||
*/
|
||||
if (ee->engine.func->fn_evas_changed)
|
||||
ee->engine.func->fn_evas_changed(ee, rend);
|
||||
ee->engine.func->fn_evas_changed(ee, change);
|
||||
}
|
||||
#ifdef ECORE_EVAS_ASYNC_RENDER_DEBUG
|
||||
if ((ee->in_async_render) && (ee->async_render_start <= 0.0))
|
||||
|
|
Loading…
Reference in New Issue