evas: Use efl_gfx APIs where appropriate
authorJean-Philippe Andre <jp.andre@samsung.com>
Mon, 20 Jun 2016 05:11:32 +0000 (14:11 +0900)
committerJean-Philippe Andre <jp.andre@samsung.com>
Mon, 20 Jun 2016 05:11:32 +0000 (14:11 +0900)
commitccaf12e1b66b2b491fc9bd434f646528bff06526
tree0bdb418cbfbf8fa0c800ca719810be2f72fd6b44
parent17a51cffd3c5ded9364acc18a8bb3f21bfc5edf7
evas: Use efl_gfx APIs where appropriate

This is a better fix than the previous patch, as it keeps
the legacy API check. The point of that check is: if the object
has been created with legacy API (evas_object_image_[filled_]add,
then legacy APIs are allowed, otherwise they are disallowed. This
means only EO APIs should be used on an eo_add() image object.
src/lib/evas/canvas/evas_image_legacy.c
src/lib/evas/canvas/evas_object_image.c