Did not realize this list existed, forwarding. Sorry for the mixup. ~ C. ---------- Forwarded message ---------- From: Corbin Simpson <[email protected]> Date: Sat, Dec 12, 2009 at 10:34 PM Subject: [pyglet] Sprites, matrices, etc. To: [email protected]
Hey, mate. I've been working on a small game engine, using pyglet+cocos, and I've found a bit of a problem with a couple Sprite-related things. First, Sprite doesn't use GL's modelview matrices to do its scaling, rotation, etc. This wouldn't be a big deal, except that cocos doesn't really respect that (cocos.sprite.Sprite overrides draw() without adding any functionality) and as a result a couple of my Sprite-based classes are a bit on the bloated side. I've got a TiledSprite class that derives from Sprite and has the ability to tile its texture arbitrarily. I'd like to upstream this since it's icky to have in my code and pyglet's license requires it, but right now it doesn't work with scaling/rotate and I'm not keen on adding that in unless Sprite can be changed to do matrices. Speaking of which, ARB_npot isn't properly supported. I attached a patch in the issue tracker that should provide correct NPOT support when available, falling back to rectangles correctly, etc. but haven't seen any movement on that yet. So, what are your thoughts on this? I'd really like to get as much of my graphics code upstream as possible; it makes my life easier. ~ C. -- Only fools are easily impressed by what is only barely beyond their reach. ~ Unknown Corbin Simpson <[email protected]> -- Only fools are easily impressed by what is only barely beyond their reach. ~ Unknown Corbin Simpson <[email protected]> -- 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.
