Re: Quesa on Intel woes. Does Quesa support only native byte order?

[James W. W. <ja...@fr...>]

I wrote:

>>Exactly what did you change?  Do you mean pass the wrong value for
>>pixmapDrawContextData.pixmap.byteOrder, which would just be a case of
>>false advertising, or do you mean that you removed the
>>kNativeEndianPixMap flag from the NewGWorld calls in QutTexture.c?


"Sean McBride" <se...@ro...> wrote:

>The former.  So the behaviour makes sense given that Quesa always works
>in native endianness.  If I change the latter, then the triangle becomes
>awash in blue (expected) but the background image does not get swapped,
>why is that?

The background image is not being handled by Quesa, it's just set up 
with a QuickTime image importer and copied with CopyBits.  Clearly 
those APIs can handle non-native-order GWorlds.
-- 
   James W. Walker, Innoventive Software LLC
   <http://www.frameforge3d.com/>