On Jan 28, 2008 2:42 PM, Nathan <[EMAIL PROTECTED]> wrote: > I ran the docs/tests/tests.py or something like that, and went through > quite a few tests, but got stuck at the fullscreen tests. An > unresponsive black window replaces my background on the fullscreen > test and then won't get away. I thought it might be because I left a > previous test in keyboard-exclusive mode, but I ran through the tests > a second time just closing each window without doing anything, and it > got stuck at the first fullscreen test. > > I attached two of the test logs. > > What next? My app doesn't even use fullscreen, so that's not the > problem that's making the graphics all wacky.
The fullscreen error is a real problem I've not seen before; I opened issue 225 http://code.google.com/p/pyglet/issues/detail?id=225 to track it. If you're interested in debugging it, the first step is to copy the "aglcheck()" line upwards until you find the earliest point of failure (probably around aglSetFullScreen). Also supply your display details as reported in gl_info.py and the Apple System Information panel so that a workaround can be isolated for your system if one is found. The easiest way to run the remaining tests is to comment out or delete the tests that don't work from tests/plan.txt. You could also isolate a particular group of tests; in your case the interesting ones are probably in: python tests/test.py image 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 -~----------~----~----~----~------~----~------~--~---
