From 56ec38f75909d4d00662e0b383abb8e78505d327 Mon Sep 17 00:00:00 2001 From: Hermet Park Date: Thu, 17 Jan 2019 19:32:40 +0900 Subject: [PATCH] evas vg: correct max frame number. Change-Id: I97ea57cca8dc22a2810390ef1bb096ce2d92d7fe --- src/lib/evas/canvas/efl_canvas_vg_object.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/lib/evas/canvas/efl_canvas_vg_object.c b/src/lib/evas/canvas/efl_canvas_vg_object.c index 3283270..f85e62e 100644 --- a/src/lib/evas/canvas/efl_canvas_vg_object.c +++ b/src/lib/evas/canvas/efl_canvas_vg_object.c @@ -775,7 +775,7 @@ _efl_canvas_vg_object_render(Evas_Object *eo_obj EINA_UNUSED, We assume the first and last frame images are the most resusable in generic scenarios. */ if (pd->frame_idx == 0 || - (pd->frame_idx == (int) evas_cache_vg_anim_frame_count_get(pd->vg_entry))) + (pd->frame_idx == (int) (evas_cache_vg_anim_frame_count_get(pd->vg_entry) - 1))) cacheable = EINA_TRUE; if (pd->vg_entry) -- 2.7.4