On Wed, Mar 9, 2011 at 12:43 AM, Phillip Nguyen <[email protected]>wrote:

> On Mar 8, 5:35 pm, Tristam MacDonald <[email protected]> wrote:
> > It runs beautifully for me on the default system Python and pyObjC, on a
> > fully-upgraded installation of OS 10.6.6.
> >
> > Well, beautifully apart from image loading, which appears to be
> completely
> > broken.
>
> Where is the image loading failing?  Since the image decoder imports
> the quartz module inside a try block and falls back to a (very slow)
> default loader if it encounters an exception, you might have to edit
> the pyglet/image/codecs/__init__.py file to get rid of the try-except
> surrounding the import.  Or are you saying that it is importing the
> correct module but the loaded images are not appearing correctly?
>

I haven't had the time to dig into it, but according to the stack trace it
looks like it might just be an incorrect pyobjc call somewhere in the codec:

  File "/Users/swiftcoder/Developer/pyglet/pyglet/resource.py", line 500, in
image
    identity = self._cached_images[name] = self._alloc_image(name)
  File "/Users/swiftcoder/Developer/pyglet/pyglet/resource.py", line 444, in
_alloc_image
    img = pyglet.image.load(name, file=file)
  File "/Users/swiftcoder/Developer/pyglet/pyglet/image/__init__.py", line
186, in load
    image = decoder.decode(file, filename)
  File "/Users/swiftcoder/Developer/pyglet/pyglet/image/codecs/quartz.py",
line 134, in decode
    image = self._get_pyglet_ImageData_from_source_at_index(sourceRef, 0)
  File "/Users/swiftcoder/Developer/pyglet/pyglet/image/codecs/quartz.py",
line 121, in _get_pyglet_ImageData_from_source_at_index
    CoreFoundation.CFDataGetBytes(imageData, byteRange, buffer)
TypeError: Don't know how to convert to extract count: {_CFRange=ii}

-- 
Tristam MacDonald
http://swiftcoder.wordpress.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.

Reply via email to