|
From: James W. W. <os...@jw...> - 2006-03-17 17:14:58
|
On Mar 17, 2006, at 7:33 AM, Sean McBride wrote: > On 2006-03-16 10:30, James W. Walker said: > >> I asked about this on the Mac OpenGL mailing list, and it is an >> endian issue. As you say, NewGWorld is treating the bytes as xRGB >> order, whereas OpenGL on Intel uses BGRA order. > > I'm on the ogl mailing list, though don't read it generally, and I > took > a look at the thread you started. > > But I'm not sure of the conclusion. What I neglected to mention is that I received a clarification off- list from an Apple OpenGL engineer. > Is there a Quesa bug? An OGL bug? > A QD bug? Or it is just something Quesa clients need to do > differently > on intel? I'd say it's a mismatch between the way QD does things and the way OGL does things. The fact that Quesa ignores the endian information given to it seems like a bug. > Should we create all our GWorlds with the kNativeEndianPixMap > flag? Would that fix it? I would guess that would work. I wasn't aware of the kNativeEndianPixMap flag. |