On Apr 10, 12:01 pm, Zachrahan <[EMAIL PROTECTED]> wrote: > Thanks, Saroj! I really appreciate the sample code. I'll dig around in > sympy a bit more to check the related things out. > > One question -- it looks like this setup allows only one window at a > time (because the window obtains the gl_lock). Is this the case?
It looks like it is the case > Presumably more complex schemes could be run in a background thread > similarly -- as long as pyglet.app.run() is fired off in the > background thread, and only one thread at a time tries to do any GL > calls? > > Thanks again -- and I'll report back with my findings... > > Zach The current sympy code which uses pyglet 1 can have multiple windows. This code is my modification to see if pyglet 1.1 will solve the CPU usage problem and it did. I haven't played much after that because I am busy with school. My guess is the gl_lock release is not in the appropriate position in the above case. I will post if I do something better with the code anytime soon. I am sure I will start improving sympy plotting code as soon as my school ends at the end of this month. My guess is you will improve the code sooner than that. Please share with us ;) Also, is the pyglet window closing for you on pyglet 1.1alpha2? I am running KDE 4.0.3 and even the pyglet examples' windows are not closing when I press the close button. I am not sure if it is a pyglet bug.. just making sure before reporting it. Anyone? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
