Strange because I reread my post and I've got all attachments. The idea to encode to memory is because I want to store images on database and users will select an image on disk, resize it and then I use this Fl_Image that is already loaded and shown to encode it back to png or jpeg and save to database (resized, cropped, thumbnail, ...).
If we have it on memory we ca also save to a file, but my choice on this application is to avoid disk usage as much as possible. Please try with another program to see if you can access the attachments. Thanks for your attention ! On Thu, 12 May 2011 18:18:49 +0200, MacArthur, Ian (SELEX GALILEO, UK) <[email protected]> wrote: > Domingo, > > Looks like your attachments were stripped - at least, they never got > here... > >> It seems that some colors are inverted or missing on jpg >> images and on png >> they seen to skip dome colors. > > Hmm, tricky; my code writes to file either PNG or JPEG and I've never > had any problems... I wonder what went wrong with yours? > > The subject line says "encode to memory" so maybe there's something odd > going on there? > > Why encode an image to memory though? > Surely, if you want it "in memory" then the default fltk pixelmap is > more useful? > > >> Attached is a fluid project and a patch to add a static >> method "encode" to >> Fl_PNG_Image and Fl_JPEG_Image, when they work properly I >> propose then to >> be added to official fltk distribution. > > Possibly too late for 1.3. then! > > Maybe for the next iteration though... > > > > SELEX Galileo Ltd > Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex > SS14 3EL > A company registered in England & Wales. Company no. 02426132 > ******************************************************************** > This email and any attachments are confidential to the intended > recipient and may also be privileged. If you are not the intended > recipient please delete it from your system and notify the sender. > You should not copy it or use it for any purpose nor disclose or > distribute its contents to any other person. > ******************************************************************** > -- Using Opera's revolutionary email client: http://www.opera.com/mail/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
