|
From: Sean M. <se...@ro...> - 2006-03-17 21:19:35
|
On 2006-03-17 09:14, James W. Walker said: >What I neglected to mention is that I received a clarification off- >list from an Apple OpenGL engineer. Ah. :) >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. OK, is it something you can fix=3F :) >> Should we create all our GWorlds with the kNativeEndianPixMap >> flag=3F Would that fix it=3F > >I would guess that would work. I wasn't aware of the >kNativeEndianPixMap flag. It's here: <http://developer.apple.com/documentation/MacOSX/Conceptual/ universal=5Fbinary/universal=5Fbinary=5Ftips/chapter=5F5=5Fsection=5F15.htm= l> I'd like to try adding kNativeEndianPixMap in the 'Background Test' but I don't see any NewGWorld calls at all. So searched all of Quesa and added the flag to every NewGWorld call. I'm not sure if that's something you'd want to make permanent, but it did fix the problem in 'Background Test'. I'll have to try with our real app next... -- =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F Sean McBride, B. Eng se...@ro... Rogue Research www.rogue-research.com Mac Software Developer Montr=E9al, Qu=E9bec, Canada |