[E-devel] [PATCH] Make sure image colorspace is properly set

[Andre M. <and...@gm...>]

Hi,

I found a bug when using the engine 16 bits and trying to set the
image colorspace if it's different from EVAS_COLORSPACE_565_A5P.

The problem is that when I call evas_object_image_colorspace_get it
uses the engine func colorspace_get to return the current colorspace,
so I tested if it was different from EVAS_COLORSPACE_565_A5P, and if
TRUE I was setting the colorspace to EVAS_COLORSPACE_565_A5P. Then I
was trying to set the data using evas_object_image_data_set and it was
failing with:
  Unsupported colorspace 0 in eng_image_new_from_copied_data()
(evas_engine.c:427)

The method evas_object_image_data_set is using o->cur.cspace as the
current colorspace and the evas_object_image_colorspace_get doesn't.
This is inconsistent and it's causing this bug.

The attached patch proper init o->cur.cspace to the engine
colorspace_get and uses it on evas_object_image_colorspace_get.

Ok to commit?

BR

-- 
Andre Moreira Magalhaes (andrunko)
--------------------------------------------------------
Jabber: and...@gm...
MSN:   and...@ms...
Skype:  andrunko
Blog:    http://andrunko.blogspot.com