Revert "evas: fix a map rendering problem."

This reverts commit 9fcd03952e.

Just noticed from ManMower, this caused a side-effect that drops
enlightenment performance. I need to check it seriously then
decide again how this patch to be.
This commit is contained in:
Hermet Park 2018-06-05 20:58:35 +09:00
parent 5a4f16531f
commit 77684dc53a
2 changed files with 3 additions and 10 deletions

View File

@ -838,6 +838,7 @@ evas_object_render_pre_effect_updates(Eina_Array *rects, Evas_Object *eo_obj, in
if (!obj) return;
if (!obj->layer) return;
if (obj->is_smart) goto end;
/* FIXME: was_v isn't used... why? */
if (!obj->clip.clipees)
{

View File

@ -1710,19 +1710,11 @@ evas_object_smart_render_pre(Evas_Object *eo_obj,
Evas_Object_Protected_Data *obj,
void *type_private_data EINA_UNUSED)
{
int is_v, was_v;
if (obj->pre_render_done) return;
if (obj->changed_map || obj->changed_src_visible)
{
evas_object_render_pre_prev_cur_add(&obj->layer->evas->clip_changes,
eo_obj, obj);
is_v = evas_object_is_visible(eo_obj, obj);
was_v = evas_object_was_visible(eo_obj,obj);
evas_object_render_pre_effect_updates(&obj->layer->evas->clip_changes,
eo_obj, is_v, was_v);
}
evas_object_render_pre_prev_cur_add(&obj->layer->evas->clip_changes,
eo_obj, obj);
obj->pre_render_done = EINA_TRUE;
}