Yes, sorry I haven't been able to get back to you. I have some free time coming up in a week or so. I thinking that it might be a good time to just bring all of the code from the cocoa-ctypes clone into the normal repository and drop PyObjC. I can't really think of any good reasons anymore for keeping it.
--phillip On May 11, 11:13 am, Winston Wolff <[email protected]> wrote: > Phillip-- > > Are there plans to roll this version of the quartz image decoder back into > the regular pyglet repository? > > >>>>http://code.google.com/r/evilphillip-cocoa-ctypes2/ > > -Winston > > On Apr 20, 2012, at 10:41 AM, Winston Wolff wrote: > > > > > > > > > Phillip-- > > > Yay, your version of the quartz image loader works great! Thank goodness. > > > I'll just comment on a funny effect of the pre-multiplying, but I'm not > > complaining--your fix is great and I can start working on my prototype > > again. I have one image with a white background, but different alphas in > > different parts of the solid-white background as a result of erasing parts > > of my original image in my image editor. That makes funny dark lines > > appear. I can fix my image. > > > -Winston > > >>>> 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 > > > Winston Wolff > > Stratolab - Games for Learning > > tel: (917) 543 8852 > > web:www.stratolab.com -- 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.
