On Tue, Oct 7, 2008 at 8:41 PM, Grzegorz Adam Hankiewicz <[EMAIL PROTECTED]> wrote: > > El 04/10/2008, a las 22:46, David Eyk escribió: > >> Silly me. I just did a better search of the archives. Looks like a >> hardware limitation. Sorry for the spam. > > I also search the archives, finding > http://groups.google.com/group/pyglet-users/browse_thread/thread/64bd227ea177a718/aa117c14b4a25fd3?lnk=gst&q=GLException+image+big#aa117c14b4a25fd3 > , but rather than knowing this is a hardware limitation (which I > already knew it is), I would be glad to hear suggestions on how to > come around the issue. > > Say, splitting the image and loading several quads which then are > blitted on the screen. How can be this accomplished in pyglet? I was > expecting to find some ideas or source code in the mail archives but > didn't.
The image.get_region() method can be used on an ImageData to return just part of the image, which can then be get_texture()'d and blit()'d separately. Alex. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
