On Nov 19, 11:48 pm, Nathan <[email protected]> wrote: > 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.
Yeah, I saw where it doing it, I just wanted to know if I could count on that behavior or if it was a bug that would eventually be fixed. I've written a C extension to blit the tiles and that code needs it to be one way or the other consistently. For now, I can control it by the size of the atlas. > That seems like a pretty big image to be making an atlas of. I am using the atlas to store a currently unknown number of 16x16 tiles. I just picked 1024x1024 as a starting point. >Are you sure this behavior happens with _any_ image with a size that's a power > of 2? (e.g. 64x64?) So far I've only added 16x16 and 256x16 images, but they are both one way or the other depending on the power of 2-ness of the atlas. Thanks -- 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.
