What are your general opinions on the following two issues? 1. The lack of monitor resolution changing capability 2. The fact that image.Texture.blit_into() isn't alpha-aware
The bottom two URLs link to more specific info/discussion about these issues, to which Alex has basically responded to saying he thinks it's out of pyglet's scope to implement these two features. I highly disagree. I mean, I'm not demanding here 'ALEX: CODE THIS STUFF'.. but I'm saying why completely reject them? Maybe put them on the 'to do slate', if not at least say something like 'if someone codes it, i will include it'? I mean the way Alex is currently responding is as if someone hands him the code he won't even be willing to add it to pyglet..? I think these two are both _utterly_ in the realm of pyglet _and_ are pretty significant things to have. :) 1. http://groups.google.com/group/pyglet-users/web/issues-with-full-screen-resolution 2. http://code.google.com/p/pyglet/issues/detail?id=340&can=1&sort=-id&colspec=ID%20Status%20Type%20Milestone%20OpSys%20Summary Cheerio! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
