Why is the imagedata value different from Win32 to MacOS platforms?

[Peter T. Evensen]

Is this an endian issue?

At 09:32 AM 7/25/2006, you wrote:


>Joel ,
>
>I don't know it's related, but I remember that, when building an external in C
>for image processing, I found that the RGB values of each pixel was in a
>different order on Mac and on Win. Therefore I had to swap the 3 values on
>Win to get the correct order in Rev (actually MC)... I don't remember what the
>Win order was though...
>
>So if I were you, I'd try swaping the 3 values until I get the right order...
>This can be done easily by "forcing" some pixel values in an imagedata to
>R=255, G=0, B=0
>R=0, G=255, B=0
>R=0, G=0, B=255
>
>JB
>
>
> > For image processing I have to extract the RGB values from an
> > imagedata of an image but I got different results under MacOSX and
> > Win32.
> > I found that the imagedata values is different between the two
> > platform: every color component of pixels is slighty changed. I have
> > not found in the documentation such a change depending on the
> > platform. Notice that <the text of image> is identical between both
> > platform.
> >
> > Could anyone give me a clue?
> >
> > Is there an easy other way to get the exact RGB array on both platforms?
> >
> > Thanks!
>
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your 
>subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution

Peter T. Evensen
http://www.PetersRoadToHealth.com
314-629-5248 or 888-682-4588