Hello

maybe you can use int mkfifo (const char *FILENAME, mode_t MODE) to create a
FIFO in your application. You can then invoke imlib2 with this filename. You
must feed this FIFO with you data.

Anyway if you explain why you must have your jpeg in memory I can help more.

You probably want to decompress your jpeg. You can rip the loader code if it
quicken your app however.

Regards

Michel

Carsten Haitzler (The Rasterman) a écrit :
> On Wed, 23 Feb 2005 13:14:25 +0100 Antonio Larrosa Jim__nez <[EMAIL 
> PROTECTED]>
> babbled:
> 
> 
>>Hello,
>>
>>I have the contents of a jpeg file in memory and I'd like to do some 
>>operations on it before writing it to disk, so I'd like to open the file 
>>without having to save it to disk, then use imlib_load_image( filename )  and
>>then removing the temporary file.
>>
>>The kernel is of course caching the disk, but if I use imlib2 for its speed, 
>>then I'd prefer not to introduce a temporary file when the file contents are 
>>already loaded in memory. The problem is tht I didn't find how to do it in 
>>the docs.
>>
>>Is there any way to open an image from a memory buffer ?
> 
> 
> unfortunately (for you) we never provided an api to do that. though possible 
> via
> a loader - no loaders support it :( sorry. epeg does support this, BUT it will
> only give you RGB data... :)
> 



-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to