On 21/09/2009, at 7:28 PM, Tartley wrote:
> Although, to be honest, with hindsight I realise that I am confused
> about how my own code was working. How come setting the opengl
> projection/modelview matrices affected the image.blit()? Presumably
> it's not a real old-school "blit" as I understand the word, but is
> simulating one using a texture mapped quad? Or am I completely
> confused?
Ah, well in one sense you're correct (a blit does actually write
pixels to a frame buffer just like the Old Skool) but in the other
sense you're ... correct in that your projection / modelview affects
how that blit will write itself to the frame buffer. The default
projection pyglet sets up makes sure that there's a 1-1 correspondence
between your image blits and the frame buffer. Mess with that
projection and it's not going to look correct any more.
Richard
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pyglet-users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/pyglet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
