Hello Rob, Thanks for your reply. A lot of people seem to like pyglet, and I think it somehow needs more visibility. Perhaps publishing a new 1.2 release and announcing this around on reddit or hacker news might help a bit to get more people interested.
I will have a look at the bug tracker and see what I could fix. I don't know yet if I will be using pyglet for the upcoming project though. It's menuing with some 2d graphics for an appliance and they want it asap (as usual). :-) On Saturday, 8 August 2015 10:18:21 UTC+1, Rob wrote: > > Hi, > > I will probably create a new 1.2.x bugfix version with some of the latest > fixes as it will probably take some time to stabilize 1.3. > > Issue #51 was caused by in incorrect interpretation of the GLX api. It > probably surfaced due to changes in GLX. Pyglet was incorrectly using some > value inside an opaque struct. The contents of this struct are for GLX > internal only, so they can change without warning. Probably the value read > by pyglet did change, causing the issues. I must say when I read the API > docs I was also confused by the description and at first thought pyglet was > right. > > Pyglet did hit a rough patch some time ago, because simply nobody had time > to maintain it. Recently I started maintaining it and released the 1.2.x > versions. For 1.3 I am focussing on improving the quality and test coverage > and making it easier to maintain Py2 and Py3 compatibility using python > future. > > But currently I am still mostly on my own, so more contributors are > definitely welcome. Don't hesitate to create pull requests, I will evaluate > them and pull them in. Until now I was only able to support Linux and > Windows, but as of this week I also have Mac hardware to test and develop > on (for my day job I have to support Linux, Windows, Android and since > recently OSX and iOS). > > I hope we can make pyglet the best Python OpenGL framework out there ;-) > > Rob > > Op zaterdag 8 augustus 2015 02:15:55 UTC+2 schreef Jason Spashett: >> >> I've been getting this issue regualrly on all linux installations while >> playing with pyglet. I see it's fixed now in the repository but it's not in >> pypi yet. I have a few miscellanous questions: >> >> presumably it will get a pypi update for this at some point >> >> The issue has been present since 2008, the first commit, how come it's >> only surfaced now? Is it the result of glx or other changes? >> >> I ask these questions as I am thinking of using pyglet for a comercial >> project for a client, and of course I am a little aprehensive in case i run >> into trouble with pyglet. >> >> However, pyglet seems to be exactly what I need, unless I waste effort >> going the DIY route. >> >> I saw some rumors of pyglets demise, but perhaps the project just needs >> more contributors. >> >> Thanks, >> >> Jason >> >> >> >> -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to pyglet-users+unsubscr...@googlegroups.com. To post to this group, send email to pyglet-users@googlegroups.com. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
