On Jan 27, 2008 8:52 PM, Alex Holkner <[EMAIL PROTECTED]> wrote: > 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
Oh, wow. Well, I'm out of time for tonight. I _am_ interested in debugging this, but I don't have much spare time (wife, kids, job, etc.), so it'll probably be several days before I'm able to get back to this. I'll let you know what I find when I do. ~ Nathan --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
