On Sun, Jun 22, 2008 at 7:14 AM, Richard Jones <[EMAIL PROTECTED]> wrote:
> On Sun, Jun 22, 2008 at 7:21 PM, Lucio Torre <[EMAIL PROTECTED]> > wrote: > >> On Sat, Jun 21, 2008 at 8:35 PM, Alex Holkner <[EMAIL PROTECTED]> >> wrote: >> >>> This is an interesting example, that actually demonstrates a problem >>> with your video card, as well as exposing some of the internal >>> heuristics used by pyglet. I hope you like messy details... >>> >> >> Is there any way to have this kind of 'bad video card' problems solved by >> pyglet? Ive seen a lot of issues where this happens, and people are still >> using 3dgames, 3d desktops and 3d everything, and asking them to upgrade or >> buy a new video card is not always possible if i want them as users of >> whatever i develop. >> > > If you look in the pyglet source you'll see there's already a bunch of > work-arounds like the ones you describe :) > > Resources are the main roadblock, rather than absence of any sort of > willingess. > Nice! And please dont take it as a criticism for your work, just a misunderstanding in direction. Regards, Lucio. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
