On Fri, 28 Sep 2007 17:01:18 -0300 "Andre Magalhaes" <[EMAIL PROTECTED]> babbled:
> 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? that seems ok to me! sim - commit porfavor! -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [EMAIL PROTECTED] 裸好多 Tokyo, Japan (東京 日本) ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
