Pepjin, I don't believe I had any "quick time" issues. Stonewall Ballard's replies above worked for the issue I did have, though this limits my ability to deploy a production Pyglet application with other Mac users. The issue appears to have something to do with OSX saving the state for windows automatically, which then allows the operating system to restore the window's geometry and last opened documents the next time a particular application is launched. This behavior isn't specific to Python...if you browse your "~/Library/Saved Application State" directory, you will see many such entries for a variety of applications. In this case, the offending one that must be deleted is org.python.python.savedState. However, as Stonewall Ballard noted above, you must actually lock this file somehow to prevent it from being recreated each time Pyglet runs.
Thanks to all who helped me with this issue. I am now running a pure-Python OpenGL application, and am very impressed with Pyglet. I don't have any additional information on this issue, but would be happy to lend my time and Macs to tracking down the cause. Best regards, Steve On Thursday, December 6, 2012 4:39:28 PM UTC-7, pepijn wrote: > > Hey Nathan/all, > > Thanks for outlining these steps. Unfortunately i'm still getting the same > quick time errors as Steve Willis above. I had previously installed Pyglet > 1.1.4 through pyglet.org... Maybe i should've uninstalled that one before i > followed your steps. Not sure how to uninstall though. I looked through > their documentation but they only tell you how to install. Anyone any ideas? > > Also, can i use the stock python that comes with os x 10.8? > > Thanks for all the help here in any case! > > Pepijn > > On Thursday, November 1, 2012 1:04:15 PM UTC-7, Nathan wrote: >> >> On Thu, Nov 1, 2012 at 10:16 AM, Steve Willis <[email protected]>wrote: >> >>> I would suggest downloading and trying it. That said, as I posted >>> before, it does not seem to be working for me. There was mention of >>> committing a fix for OSX Mountain Lion in earlier discussions. I have not >>> been able to determine if that fix made it to the Mercurial repository. If >>> it did, either I am not savvy enough to clone the correct revision >>> (completely plausible), or the committed fix doesn't work on my system. I >>> feel somewhat confident in conveying the current (as of last week) >>> [snip] >>> >> Steve >>> >> >> The following commands run in the terminal ought to get you the latest >> pyglet 1.2dev: >> >> (First install mercurial from http://mercurial.selenic.com/ ) >> hg clone https://pyglet.googlecode.com/hg/ pyglet >> cd pyglet >> hg pull >> hg update >> sudo python setup.py install >> >> ~ Nathan >> > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To view this discussion on the web visit https://groups.google.com/d/msg/pyglet-users/-/jKhZZizkFNUJ. 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.
