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

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

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

>In gldrawcontext_mac_new() in the kQ3DrawContextTypePixmap case there is
>an assertion checking that the byte order passed in is the same as the
>CPU's byte order.  This assertion is new in 1.8.  Why is it there?  Does
>Quesa only support native byte order?

Correct.

>  That is, can I not provide a big
>endian buffer on a little endian system or vice versa?

Currently not.  Why do you want to?

>  If I change the
>"Background Test" in such a way that I pass the wrong byte order I get
>the assertion but the app still works (no images are byte swapped).

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?
-- 
   James W. Walker, Innoventive Software LLC
   <http://www.frameforge3d.com/>