On 06/08/2007, at 10:56 AM, mithrandi wrote:
> > On Aug 6, 12:28 am, Alex Holkner <[EMAIL PROTECTED]> wrote: >> unknown) or to use the polymorphic functions. No extra setup is >> required to do this: pyglet.gl and PyOpenGL function calls can be >> freely intermixed. > > My only concern is that this may not necessarily be the case; for > example, I think there is some internal bookkeeping done in PyOpenGL > regarding glBegin/glEnd; calling the pyglet.gl versions of these could > then cause problems. But, I suppose there are probably not too many You are correct in this case, pyglet also maintains its own state here when error checking is enabled. I would assume that any developer would not be mixing libraries between glBegin/glEnd blocks. > cases where this is a problem; the duplication of effort is of mild > annoyance, but since the pyglet interfaces are low-level and (mostly? > completely?) autogenerated, I suppose it isn't that much of a concern. The scripts for (re)generating the pyglet.gl modules are in the tools/ directory. Downloading the latest header(s) and rerunning the script on the appropriate platform is sufficient to update pyglet's wrap. It would be nice if some cron job recognised a new GL release and initiated this automatically, but probably unnecessary :-) Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
