On Apr 13, 7:29 pm, Winston Wolff <[email protected]> wrote: > I've spent another day digging into this problem. I made a test png with just > four pixels so I can see the data. It is indeed being decoded as all zeros. > > I was able to get QuartzImageDecoder to work one time, but I can't reproduce > it. I was experimenting running the OSX default python2.6 instead of my > framework build 2.7.2 in virtualenv. > > I'm using virtualenv and pyobjc v2.2. Does anybody know of incompatibilities > with pyglet, virtualenv, and pyobjc2.2?
Winston, Could you send me your test png image and I'll see what happens on my end. Also could you try running your example with the evil-phillip- cocoa-ctypes2 pyglet clone here: http://code.google.com/r/evilphillip-cocoa-ctypes2/ and see if there is any difference? Pyglet has issues with PyObjC 2.2. However it works with the default PyObjC installed with OS X 10.6 which is version 2.2b3 (beta 3). If you're using your own installation of pyobjc, you should try to use version 2.3 or greater. If it does turn out to be a PyObjC issue, I can possibly rewrite the quartz image decoder to not use it. --phillip -- 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.
