Gary, I don't have any previous experience with that portion of pyglet, but looking at the source code for TextureAtlas (image/atlas.py:208 from hg tip), it appears that it intends to return a TextureRegion with the same pixel-dimensions as the original image.
So my guess would be that that's a bug. That seems like a pretty big image to be making an atlas of. Are you sure this behavior happens with _any_ image with a size that's a power of 2? (e.g. 64x64?) ~ Nathan On Sat, Nov 19, 2011 at 9:25 PM, Gary Daniels <[email protected]> wrote: > > I noticed that if I create a TextureAtlas with a power of 2 size > (1024x1024), the tex_coords of a 16x16 image added are: > > (0.0, 0.0, 0.0, 0.015625, 0.0, 0.0, 0.015625, 0.015625, 0.0, 0.0, > 0.015625, 0.0) > > With a size of 1023x1023 (or any non-power of 2), they are pixel > based: > > (0.0, 0.0, 0.0, 16.0, 0.0, 0.0, 16.0, 16.0, 0.0, 0.0, 16.0, 0.0) > > Is this intentional? > > > -- > 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. > > -- 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.
