Hi! > > The issue was simply that you were assuming a different byte order > than the one used on your machine. > To avoid having these issues, always access whole pixels.
Can you be a little more explicit there ^^? I don't imagine other way than access the data directly by pixel channels. > Some documentation about pixel formats can be found here: > http://cairographics.org/manual/cairo-Image-Surfaces.html#cairo-format-t > As you can see, ARGB32 is a 32-bits format stored native-endian. > > I hope this helps, but don't hesitate to ask for more clarification if > it is not sufficient. > > Andrea > Thanks to you too! -- Carlos http://synfig.org ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
