On Thu, Sep 24, 2009 at 4:12 PM, Cedric BAIL wrote:
>
> Hum, sorry my bad. I didn't read that code since sometime and in fact
> I don't see why info.loader could be NULL. It is set by
> evas_common_load_rgba_image_module_from_file when it try to find the
> right loader. So this change my diagnost
On Thu, Sep 24, 2009 at 3:59 PM, Mikael Liljeroth
wrote:
> On Thu, Sep 24, 2009 at 5:46 AM, Cedric BAIL wrote:
>> info.loader is removed when loading is done. So if it's gone, my guess
>> is that the data has already been loaded. Is it a possible explanation ?
> info.loader is null even before i
On Thu, Sep 24, 2009 at 5:46 AM, Cedric BAIL wrote:
>
> info.loader is removed when loading is done. So if it's gone, my guess
> is that the data has already been loaded. Is it a possible explanation
> ?
>
>
info.loader is null even before i call the evas_cache_image_load_data for
the first time.
On Thu, Sep 24, 2009 at 2:32 PM, Mikael Liljeroth
wrote:
> On Thu, Sep 24, 2009 at 5:19 AM, Mikael Liljeroth <
> [email protected]> wrote:
>> Hi, I have encountered a rather strange problem when testing revision 42549
>> of the efl libraries.
>> The problem seems to be related to images a
Hi, I have encountered a rather strange problem when testing revision 42549
of the efl libraries.
The problem seems to be related to images and the evas image loaders.
I'm using a custom built evas engine that uses
evas_common_load_image_from_file and then
the evas_cache_image_load_data to load the
On Thu, Sep 24, 2009 at 5:19 AM, Mikael Liljeroth <
[email protected]> wrote:
> Hi, I have encountered a rather strange problem when testing revision 42549
> of the efl libraries.
> The problem seems to be related to images and the evas image loaders.
> I'm using a custom built evas engin
