On 23/06/14 10:18, [email protected] wrote: > [...] > This was with the latest stable version of pyglet rather than tip, but > is a demonstration of how conflating these types can balls things up, > even internally. Doing `a.set_data('RGBA', 4, data1)` followed by > `a.get_data('RGBA', 4)` works and returns the list, as you would > expect.
Some work was done in tip regarding this issue, but I don't know if it's completely fixed though (IIRC should be fine now, but I'm might be wrong). Could you give it a go with tip? 1.2 alpha1 is too outdated to be useful; should go away soon when we make the beta release for 1.2. > I have other issues with the image module... You can't blit_into() > anything but a texture, doing destination.blit_into(source) seems > confusing in terms of argument order, it'd be nice to be able to blit > scaled and rotated images (ie, sprites) into each other, I feel like > trying to shove everything under AbstractImage might not be a great > idea because the different types of images really are quite different > from each other... Generally, composing and manipulating images is > not as easy as it seems like it should be. But in the end those are > nitpicks, while the bytes-as-uniode-string is the only thing that's > really strictly speaking wrong. Pretty much every other part of > Pyglet I've touched has been excellent, so. Image design is not intuitive and what it needs mostly is documentation. There's already a ticket about that: https://code.google.com/p/pyglet/issues/detail?id=743 (btw, the guy creating that ticket could use some help!) Regards. Juan -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
